1. Chapter 2 Topics –Context-Level DFD –Entity-Relationship Diagrams

2. Context-Level Data Flow Diagram (DFD) DFDs focus on the data flowing into and out of the system and the processing of the data See Example in Figure 2.5, p. 36

3. Context-Level DFD Symbols Entity, a person, group, department, or system that supplies or receives information that makes up a system It is labeled with a noun

4. Context-Level DFD Symbols Process, representing the entire system It is given the number 0

5. Context-Level DFD Symbols Data flow, represented by an arrow It shows information that passes to or from the process Data flow is labeled with a noun

6. Example of DFD

9. Entity-Relationship Diagrams (E-R Diagrams) ERDs help the analyst understand the organizational system and the data stored by the organization Also defines organizational system boundary Symbols are used to represent entities and relationships

10. Three Types of Entities –Fundamental entity Describing a person, place, or thing –Associative entity Linking entities –Attributive entity Describe attributes and repeating groups

11. Relationships Relationships show how the entities are connected There are three types of relationships: –One to one –One to many –Many to many Relationship lines are labeled

12. Example of Entity-Relationship Diagram (ERD)

18. Chapter 3 Topics –Project initiation –Determining project feasibility –Manage project activities and scheduling –Manage systems analysis team members

19. 2 Reasons for Project Initiation –Problems that lend themselves to systems solutions –Opportunities for improvement through Upgrading systems Altering systems Installing new systems

20. Identify Organizational Problems by: Checking output against performance criteria –Too many errors –Work completed slowly –Work done incorrectly –Work done incompletely –Work not done at all Observing behavior of employees –High absenteeism –High job dissatisfaction

21. Identify Organizational Problems by: Listening to feedback from vendors, customers, and suppliers –Complaints –Suggestions for improvement –Loss of sales –Lower sales

22. Possibilities for Improvement –Speed up a process –Streamline a process –Combine processes –Reduce errors in input –Reduce redundant storage –Reduce redundant output –Improve system and subsystem integration

23. Feasibility Impact Grid (FIG) Is used to assess the impact of any improvements to the existing system Can increase awareness of the impacts made on the achievement of corporate objectives Current or proposed systems are listed on the left Objectives are listed on the top See Figure 3.2

24. Feasibility A feasibility study assesses the operational, technical, and economic merits of the proposed project There are three types of feasibility: –Technical feasibility –Economic feasibility –Operational feasibility

25. 1. Technical Feasibility Technical feasibility assesses whether the current technical resources are sufficient for the new system If they are not available, can they be upgraded to provide the level of technology necessary for the new system

26. 2. Economic Feasibility Economic feasibility determines whether the time and money are available to develop the system Includes the purchase of –New equipment –Hardware –Software

27. 3. Operational Feasibility Operational feasibility determines if the human resources are available to operate the system once it has been installed Users that do not want a new system may prevent it from becoming operationally feasible

28. Activity Planning Activity planning includes –Selecting a systems analysis team –Estimating time required to complete each task –Scheduling the project Two tools for project planning and control are Gantt charts and PERT diagrams

29. Estimating Time Project is broken down into phases Further broken down into tasks or activities Estimate time for each task or activity May use a most likely, pessimistic, and optimistic estimation of time

30. Gantt Charts Easy to construct and use Shows activities over a period of time See Fig. 3.7 MS Project is a good tool to prepare such diagram

31. PERT Diagram PERT - Program Evaluation and Review Technique –PERT diagrams show precedence, activities that must be completed before the next activities may be started –A network of nodes and arrows –Used to calculate the critical path, the longest path through the activities –This is the shortest time to complete the project

32. PERT Diagram Example See Fig. 3.11 p.69

33. Advantages of PERT Diagram Easy identification of the order of precedence Easy identification of the critical path and thus critical activities Easy determination of slack time, the leeway to fall behind on noncritical paths

34. Team Management Teams often have two leaders: –One who leads members to accomplish tasks –One concerned with social relationships The systems analyst must manage –Team members –Their activities –Their time, and resources

35. Goal Setting Successful projects require that reasonable productivity goals for outputs and process activities be set Goal setting helps to motivate team members

36. Project Failures Project failures may be prevented by –Training –Experience –Learning why other projects have failed