chapter1-introductiontosystemanalysisanddesign-lect.pptx

SYSTEM ANALYSIS & DESIGN  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 Inform...

SYSTEM ANALYSIS & DESIGN  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: 1. hardware 2. software 3. data 4. processes 5. people Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 1. 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. 2. Software refers to the programs that control the hardware and produce the desired information or results. a. System software manages the hardware components, which can include a single workstation or a global network with many thousands of clients. b. Application software consists of programs that support day-to-day business functions and provide users with the information they require. 3. Data is the raw material that an information system transforms into useful information. 4. Processes describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results. 5. People who have :an Reference interest Shelly in an Rosenblatt, information “Systems Analysis system are called and Design  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: Transacti on processi Managem ng ent informatio n system Decision support system Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Method: Structured Object Oriented Agile / Adaptive Analysis Analysis Method 1. Structured analysis is a 1. Object oriented analysis combines 1. Newest development traditional systems data and the processes that act techniques change over development technique that is on the data into things called time. time-tested and easy to objects. understand. 2. Attempt to develop a system 2. Use Object Oriented to model incrementally, by building a 2. Structured analysis uses a series real-world business processes series of prototypes and of phases, called the systems and operations constantly adjusting them to development life cycle user requirements. (SDLC) to plan, analyze, design, implement, and support an 3. Agile methods typically use a information system. spiral model, which represents a series of iterations, or revisions, based on user feedback. Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Method: Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 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  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Structured Analysis  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 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 Object Oriented Analysis Web-Based Catalogue  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 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, business 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. Agile/Adaptive Methods  INTRODUCTION TO SYSTEM ANALYSIS &Development System DESIGN Life Cycle (SDLC) Planni Analy Desig Developm Testin Implementa Maintena ng sis n ent g tion nce Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 1. -Plannin Identify problem -g Gather requirement 2. Analyz e Analysis detail requirement  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 3. Desig n framework Syste m serve r - Business rule – desig n clear session Database on logout - User interface relations Layout hip - Color scheme Supported - Programmi browser ng Language  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 4. Development Operation team Develope r start writing code Designer continue planning user interface Tester start building test case for test plan  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 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  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 6. Implementati 7. on Maintena nce Real user use the application - Maintain the server and system - Make larger server and database - Customer email problem - Fix the problem  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC) of Clinic Management System Project Initiation Head of Head of IT Outpatient Clinic Department (Client) (Project  Has a business Manager) idea to enhance  Arrange a the current system meeting/discuss  Send a formal ion request to IT dept which is called system request * System request can either be a system change or an improvement to the current system  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  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  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  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC) of Clinic Management System Analysis  Discuss the requirements gathered in detail (Functional and non-functional requirement)  Develop Requirements Definition Project team  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC) of Clinic Management System Analysis 1. USER REGISTRATION 2. LOGIN a) Username input field a) Username input field b) Full name field b) Password field c) New IC field c) Submit button d) Status selection d) Read user from e) Module access right database selection e) Log user into the system f) Submit button g) Save user in database 3. HOMEPAGE 4. LOGOUT a) New user should redirect here a) Logout button b) Existing users redirect here b) Clear session after login  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC) of Clinic Management System Analysis  Develop use cases  Develop data flow diagrams  Develop Entity Relationship Model (ER- D)  Deliverable - Software Requirement Specification (SRS) Project team  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  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN System Development Life Cycle (SDLC) of Clinic Management System Design  Framework - Javascript, MySQL, MariaDB  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  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)  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  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  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  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  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  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  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN 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 WaterfallANALYSIS & DESIGN Model a. This model is simple and easy to understand and use. b. It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process. c. In this model phases are processed and completed one at a time. Phases do not overlap. d. Waterfall model works well for smaller projects where requirements are very well understood. a. It is very difficult to go back and change something that was not well-thought out in the concept stage. b. No working software is produced until late during the life cycle. c. High amounts of risk and uncertainty. d. Not a good model for complex and object-oriented projects. e. Poor model for long and ongoing projects. Reference :  INTRODUCTION TO SYSTEM Spiral ANALYSIS & DESIGN Model a. High amount of risk analysis hence, avoidance of Risk is enhanced. b. Good for large and mission-critical projects. c. Strong approval and documentation control. d. Additional Functionality can be added at a later date a. Can be a costly model to use. b. Risk analysis requires highly specific expertise. c. Project’s success is highly dependent on the risk analysis phase. d. Doesn’t work well for smaller projects. Reference :  INTRODUCTION TO SYSTEM Iterative ANALYSIS & DESIGN and Incremental Development Model a. Generates working software quickly and early during the software life cycle. b. This model is more flexible – less costly to change scope and requirements. c. It is easier to test and debug during a smaller iteration. d. In this model customer can respond to each built. e. Easier to manage risk because risky pieces are identified and handled during it’d iteration. a. Needs good planning and design. b. Needs a clear and complete definition of the whole system before it can be broken down and built incrementally. c. Total cost is higher than waterfall. Reference :  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Agile Development Model a. People and interactions are emphasized rather than process and tools. b. Customers, developers and testers constantly interact with each other. c. Face-to-face conversation is the best form of communication. d. Close, daily cooperation between business people and a. In case of some software deliverables, especially the large developers. e. ones, it is difficult Continuous to to attention assess the effort technical required excellence andatgood the design. beginning of the software development life cycle. b. There is lack of emphasis on necessary designing and documentation. c. 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  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Prototyping Development Model a. Users are actively involved in the development b. Users get a better understanding of the system being developed. c. Errors can be detected much earlier. d. Quicker user feedback is available leading to better solutions. e. Missing functionality can be identified easily f. Confusing or difficult functions can be identified a. Leads to implementing and then repairing way of building systems. b. Increase the complexity of the system as scope of the system may expand beyond original plans. c. Incomplete or inadequate problem analysis. Reference :  INTRODUCTION TO SYSTEM ANALYSIS Rapid Application & DESIGN Development Model (RAD) a. Reduced development time. b. Increases reusability of components c. Quick initial reviews occur d. Encourages customer feedback e. Integration from very beginning solves a lot of integration issues. a. Depends on strong team and individual performances for identifying business requirements. b. Only system that can be modularized can be built using RAD c. Requires highly skilled developers/designers. d. High dependency on modeling skills Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Joint Development Model (JAD) a. Allows key users to participate effectively. b. 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. a. More expensive and can be cumbersome if the group is too large relative to the size of the project. Reference : Shelly Rosenblatt, “Systems Analysis and Design  INTRODUCTION TO SYSTEM ANALYSIS Leadership & DESIGN & 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  INTRODUCTION TO SYSTEM ANALYSISProject & DESIGN Management Project Activities includes identifying all project tasks and Planning estimating the completion time and cost of Scheduli Involves each. the creation of a specific timetable, ng 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 Monitori charts, Requires which are supervising, guiding, explained in and the following coordinating the ng sections. project team’s workload. The project manager must monitor the progress, evaluate the Reporti Regular results, and take corrective progress reports to action when necessary management, users, ng to control and the the project and stay on target. project team itself. Effective reporting requires strong communication skills and a Reference : Shelly Rosenblatt, “Systems Analysis and Design INTRODUCTION TO SYSTEM ANALYSISProject & DESIGN Management Activities Reference : Shelly Rosenblatt, “Systems Analysis and Design  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  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  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 INTRODUCTION TO SYSTEM ANALYSIS & DESIGN INTRODUCTION TO SYSTEM ANALYSIS & DESIGN Task 1 1. Perform a group of 2 or 3 2. Appoint a Project Manager 3. Discuss Project 1. What is Data Flow Diagram? 2. Sample DFD for Library System 3. Level 0 of DFD 4. Level 1 of DFD 5. Level 2 of DFD 6. What is Use Case Diagram