Chapter 1- INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN by DEEPA (1).pptx

Chapter 1- INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN by DEEPA

1. SYSTEM ANALYSIS & DESIGN by Siti Dianah binti Abdul Bujang Sharifah Nur binti Syed Ismail Department of Information and Communication Technology 2017

2. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN What is Information? Information is data that has been transformed into output that is valuable to users. What is Information System? Information system deals with data of the organizations. The purposes of Information system are to process input, maintain data, produce reports, handle queries, handle on line transactions, generate reports, and other output. What is Information System Components? An information system has five key components: hardware software data processes people Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 7-8

3. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Hardware consists of everything in the physical layer of the information system. For example, hardware can include servers, workstations, networks, telecommunications equipment, fiber-optic cables, mobile devices, scanners, digital capture devices, and other technology-based infrastructure. Software refers to the programs that control the hardware and produce the desired information or results. System software manages the hardware components, which can include a single workstation or a global network with many thousands of clients. Application software consists of programs that support day-to-day business functions and provide users with the information they require. Data is the raw material that an information system transforms into useful information. Processes describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results. People who have an interest in an information system are called stakeholders. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 7-8

4. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN What is types of Information? Information systems different in their business needs. It also depending upon different levels in organization information systems differ. Three major information systems are: T r ansa c tio n processing Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 10-18 M ana g eme n t information system Decision support system

5. EXERCISE Define Information - Data that has been transformed into output that is valuable to users 2. List the components of information system - Hardware - Software - Data - Processes - People 3. Which of the following is not one of the three major classes of information systems? A.  Decision support system B.  Collaboration system C.  Management information system D.  Transaction processing system Answer : B

6. EXERCISE 4. Decision support system deals with information that is required at the operational level of an organization. A.  True B.  False Answer : B 5. Which of the following is not one of the functions of an information system? A. Maintaining files B.  Producing information C.  Make decisions D.  Generate report Answer : C 6. In _________ management, information system are used to see employees’ records. A.  marketing B.  transportation C.  manufacturing D.  human resource Answer : D

7. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Method: Structured Analysis Object Oriented Analysis Agile / Adaptive Method Structured analysis is a traditional systems development technique that is time-tested and easy to understand. Structured analysis uses a series of phases, called the systems development life cycle (SDLC) to plan, analyze, design, implement, and support an information system. Object oriented analysis combines data and the processes that act on the data into things called objects . Use Object Oriented to model real-world business processes and operations Newest development techniques change over time. Attempt to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements. Agile methods typically use a spiral model , which represents a series of iterations, or revisions, based on user feedback. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 22-26

8. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Method: Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 21

9. Structured Analysis Represents the system in terms of data and the processes that act upon that data. System development is organized into phases, with deliverables and milestones to measure progress . It is called process centered technique because it focuses on processes that transform data into useful information Modelling tool – Data Flow Diagram (DFD). Uses various symbols and shapes to represent data flow, processing and storage Advantages - Traditional method, relies on written documentation, frequent phase iteration can provide flexibility comparable with other methods, well-suited to project management tools and techniques . Disadvantages - Changes can be costly, requirements are defined early and can change during development, users might not be able to describe their needs until they can see examples of features and functions. The SDLC waterfall model typically consists of five phases: a) Planning b) Analysis c) Design d) Implementation e) Support and Security INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

10. Structured Analysis INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

11. Object Oriented Analysis Views the system in terms of objects that combine data and processes. The objects represent actual people, things, transactions, and events. O-O phases tend to be more interactive. Modelling tool - Various object-oriented diagrams depict system actors, methods and messages. Advantages - Integrates easily with object-oriented programming languages, code is modular and reusable, which can reduce cost and development time, easy to maintain and expand as new objects can be cloned using inherited properties. Disadvantages - Newer method might be less familiar to development team members, interaction of objects and classes can be complex in larger systems . INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

12. Object Oriented Analysis Web-Based Catalogue INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

13. Agile/Adaptive Methods Breaks development process down into cycles, or iterations that add functionality. Each iteration is designed, built, and tested in an ongoing process. Attempts to reduce major risks by incremental steps in short time intervals . Modelling tool - Tools that enhance communication, such as collaborative software, brainstorming, and whiteboards, b usiness process modeling. Advantages - Very flexible and efficient in dealing with change, stresses team interaction and reflects a set of community-based values, frequent deliverables constantly validate the project and reduce risk. Disadvantages - Team members need a high level of technical and communications skills, lack of structure and documentation can introduce risk factors, overall project might be subject to scope change as user requirements change. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

14. Agile/Adaptive Methods

15. EXERCISE List the types of system development method - Structured Analysis - Object-Oriented Analysis - Agile/Adaptive Methods 2. Structured Analysis is based on the principle of Bottom-Up Approach. A. True B. False Answer: B 3. Which of the following is NOT TRUE regarding the waterfall method? A.  Fairly rigid approach B.  Can easily go back to previous phases C.  Good for traditional type of projects D.  Not as good for many of the new types of interactive and highly complex applications Answer : B

16. EXERCISE 4. Which of the following is the main goal of the object-oriented approach? A. Maintaining systems B. Minimizing the impact of change C. Reusability D. Functional control Answer : C 5. Agile methods seem to work best when team members have a relatively high skill level. A. True B. False Answer: A 6. What is the disadvantages of Agile Methodology? A.  Speedy and continuous delivery of the software B.  Documentation and designing take a back seat C.  Facilitates close interaction between business people and developers D.  All of the above Answer : B

17. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC) Planning Analy sis Design Development Testing Implementation Ma i n t en a n ce Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 21

18. 1. Planning Identify problem Gather requirement 2. Analyze Analysis detail requirement INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

19. 3. Design framework Sy s t e m server design Database r e l a ti o nsh ip Business rule – clear session on logout User interface Layout Color scheme P r o g r amm i ng Language Supported browser INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

20. Designer continue planning user interface Tester start building test case for test plan 4. Development Operation team Developer start writing code INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

21. 5. Testing Why testing important ??? Testing using test cases from the test plan. Validate all the requirement has been met. Make sure all the functionality are working as expected. Find as many possible bug (people cannot logout, user can’t register and etc INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

22. 6. Implementation Real user use the application 7. Ma i n t en a n ce Maintain the server and system Make larger server and database Customer email problem Fix the problem INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

23. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Project Initiation Head of Outpatient Clinic (Client) Has a business idea to enhance the current system Send a formal request to IT dept which is called system request Head of IT Department (Project Manager) Arrange a meeting/discussion * System request can either be a system change or an improvement to the current system

24. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Project Initiation Both client and project manager discuss about: - problem in the current system - what are the solutions - time factor - how will it increase the efficiency Both agrees to the terms and agreement Client then sign the agreement Project manager accept the project

25. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Planning Understanding why the system should be developed (identify the problem) and how it is suppose to be developed Deliverables - Feasibility Analysis/Study * technical feasibility (Can the system be developed?) * economic feasibility (Will it provide business value?) * organizational feasibility (If system is developed, is it usable?) - Project plan, Gantt Chart, Cost and Benefit Report Project manager and client bring the system request and feasibility analysis to the steering committee for approval Once approved, the project enters into project management

26. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Planning Staff project (Designer, Programmer, DBA, Software tester, Network Manager) - Create work breakdown structure Identify scope Identify and manage risk Gather requirements (interviews, questionnaire, observation) - User Registration - Login - Homepage - Logout Begin documentation

27. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Analysis Project team Discuss the requirements gathered in detail (Functional and non-functional requirement) Develop Requirements Definition

28. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Analysis USER REGISTRATION a) Username input field b) Full name field c) New IC field d) Status selection e) Module access right selection f) Submit button g) Save user in database 2. LOGIN a) Username input field b) Password field c) Submit button d) Read user from database e) Log user into the system 4. LOGOUT a) Logout button b) Clear session 3. HOMEPAGE a) New user should redirect here b) Existing users redirect here after login

29. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Analysis Project team Develop use cases Develop data flow diagrams Develop Entity Relationship Model (ER-D) Deliverable - Software Requirement Specification (SRS)

30. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Design Architecture design - describes the hardware/ software/ network/ - Eg . Client side, server side, web-based User interface design (GUI) - layout, color scheme (purple, grey) Program design (programming language) - ASP

31. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Design Framework - Javascript , MySQL, MariaDB

32. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Design System server design - client-server architecture - network - IP address - server System database design - database name - table names - fields

33. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Design Browser compatibility - design so that it support various browsers Mobile support - design so that it support various mobile framework Deliverables - Software Design Definition (SDD) - Database Definition Documentation (DDD)

34. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Development Operation Team will setup physical hardware (server, database) Programmers will write the code

35. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Development Designers continue to plan user interfaces Testers will start to develop test cases for the test plan Start to imagine usability of the system and see whether the user interfaces flow together Testers might discover flaws in the early stage of the system

36. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Testing Example, when testing logout function in the system, tester found out that the browser did not clear the session. An authorized user can use the computer to login, get the access to all data, manipulate the system, release bugs Testers will test based on the test cases built (Unit testing/System testing) Validate all the requirements that has been created so that all functionality work as expected Find as many bugs as possible Deliverable - Test Cases/Test Plan/Test Result

37. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Implementation The project team will get ready with the production server (install new hardware, server, scalable for production) Setting up URL links, database Some organization may start with a pilot project/launch Once everything is ready, the system will Go-Live to the real users Deliverable - Complete Functioning System

38. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Maintenance Once the system is successfully running, many users start to use the system on a daily basis, the server and environment need to be monitored. DBA has to monitor on the load, performance, storage so that it does not bring the system down at any point Larger servers, databases might be needed

39. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC ) of Clinic Management System Maintenance Bugs/errors might be found by users during production Users will write an email/call the IT dept to report the issue Programmers will then fix the bugs and deploy again Deliverable - Operational Information System

40. Life Cycle Models Waterfall model Spiral Model Iterative and incremental development Agile Model Prototyping model Rapid Application Development (RAD) Joint Application Development (JAD) INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

41. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Waterfall Model This model is simple and easy to understand and use. It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process. In this model phases are processed and completed one at a time. Phases do not overlap. Waterfall model works well for smaller projects where requirements are very well understood. It is very difficult to go back and change something that was not well-thought out in the concept stage. No working software is produced until late during the life cycle. High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. Reference : http://istqbexamcertification.com/

42. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Spiral Model High amount of risk analysis hence, avoidance of Risk is enhanced. Good for large and mission-critical projects. Strong approval and documentation control. Additional Functionality can be added at a later date Can be a costly model to use. Risk analysis requires highly specific expertise. Project’s success is highly dependent on the risk analysis phase. Doesn’t work well for smaller projects. Reference : http://istqbexamcertification.com/

43. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Iterative and Incremental Development Model Generates working software quickly and early during the software life cycle. This model is more flexible – less costly to change scope and requirements. It is easier to test and debug during a smaller iteration. In this model customer can respond to each built. Easier to manage risk because risky pieces are identified and handled during it’d iteration. Needs good planning and design. Needs a clear and complete definition of the whole system before it can be broken down and built incrementally. Total cost is higher than waterfall. Reference : http://istqbexamcertification.com/

44. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Agile Development Model People and interactions are emphasized rather than process and tools. Customers, developers and testers constantly interact with each other. Face-to-face conversation is the best form of communication. Close, daily cooperation between business people and developers. Continuous attention to technical excellence and good design. In case of some software deliverables, especially the large ones, it is difficult to assess the effort required at the beginning of the software development life cycle. There is lack of emphasis on necessary designing and documentation. The project can easily get taken off track if the customer representative is not clear what final outcome that they want. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 149

45. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Prototyping Development Model Users are actively involved in the development Users get a better understanding of the system being developed. Errors can be detected much earlier. Quicker user feedback is available leading to better solutions. Missing functionality can be identified easily Confusing or difficult functions can be identified Leads to implementing and then repairing way of building systems. Increase the complexity of the system as scope of the system may expand beyond original plans. Incomplete or inadequate problem analysis. Reference : http://istqbexamcertification.com/

46. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Rapid Application Development Model (RAD) Reduced development time. Increases reusability of components Quick initial reviews occur Encourages customer feedback Integration from very beginning solves a lot of integration issues. Depends on strong team and individual performances for identifying business requirements. Only system that can be modularized can be built using RAD Requires highly skilled developers/designers. High dependency on modeling skills Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 146

47. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Joint Development Model (JAD) Allows key users to participate effectively. The result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 144 a. More expensive and can be cumbersome if the group is too large relative to the size of the project.

48. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Leadership & Project Manager Project manager , or project leader , usually is a senior systems analyst or an IT department manager if the project is large. An analyst or a programmer/analyst might manage smaller projects. In addition to the project manager, most large projects have a project coordinator. A project coordinator handles administrative responsibilities for the team and negotiates with users who might have conflicting requirements or want changes that would require additional time or expense. Project managers typically perform four activities, or functions: planning, scheduling, monitoring, and reporting. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 144

49. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Project Management Activities Project Planning includes identifying all project tasks and estimating the completion time and cost of each. Scheduling Mo n i t ori ng Reporting Involves the creation of a specific timetable, usually in the form of charts that show tasks, task dependencies, and critical tasks that might delay the project. Scheduling also involves selecting and staffing the project team and assigning specific tasks to team members. Project scheduling uses Gantt charts and PERT/CPM charts, which are explained in the following sections. Requires guiding, supervising, and coordinating the project team’s workload. The project manager must monitor the progress, evaluate the results, and take corrective action when necessary to control the project and stay on target. Regular progress reports to management, users, and the project team itself. Effective reporting requires strong communication skills and a sense of what others want and need to know about the project. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 103

50. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Project Management Activities Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 55, 59

51. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Work Breakdown Structure Before creating work breakdown structures, you should understand the two primary chart types: Gantt charts and PERT/CPM charts. A Gantt chart is a horizontal bar chart that represents a set of tasks. Microsoft Project Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 103

52. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Work Breakdown Structure Critical Path Method (CPM) was developed by private industry to meet similar project management needs. The distinction between the two methods has disappeared over time, and today the technique is called either PERT, CPM, or PERT/CPM . Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 105

53. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Work Breakdown Structure A work breakdown structure (WBS) involves breaking a project down into a series of smaller tasks. Tasks in a work breakdown structure must be arranged in a logical sequence called a task pattern . Task patterns can involve dependent tasks, multiple successor tasks, and multiple predecessor tasks. Reference : Shelly Rosenblatt, “Systems Analysis and Design Ninth Edition”, page 110 - 119

54. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN

55. INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Task 1 Perform a group of 2 or 3 Appoint a Project Manager Discuss Project