Lecture 3 System Analysis & Design PDF

# System Analysis & Design Presented By Menna Ibrahim Gabr ## Chapter 2 Agenda - System Analyst - System Analyst Skills - Analyst Roles - System Development Life Cycle ## Introduction - The primary goal is to create value for the organization, which means increasing profits. - Many failed system...

# System Analysis & Design Presented By Menna Ibrahim Gabr ## Chapter 2 Agenda - System Analyst - System Analyst Skills - Analyst Roles - System Development Life Cycle ## Introduction - The primary goal is to create value for the organization, which means increasing profits. - Many failed systems were abandoned because the analysts tried to build a wonderful system without clearly understanding how the system would support the organization's goals, improve business processes, and integrate with other information systems to provide value. ## System Analyst - The systems analyst plays a key role in information systems development projects. - The systems analyst works closely with all project team members so that the team develops the right system in an effective way. - Systems analysts must understand how to apply technology to solve business problems. - In addition, systems analysts may serve as change agents who identify the organizational improvements needed, design systems to implement those changes, train and motivate others to use the systems. ## System Analyst Skills | Skill | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------ | | Technical | Analysts must have the technical skills to understand the organization's existing technical environment. | | Business | Business skills are required to understand how IT can be applied to business situations and to ensure real value. | | Analytical | Analysts are continuous problem solvers at both the project and the organizational level. | | Interpersonal | Analysts need to communicate effectively, one-on-one, with users, business managers, and programmers. | | Management | They need to have strong interpersonal abilities and must manage people and risks associated with unclear situations. | | And Ethical | Analysts must deal fairly, honestly, and ethically with other project team members, managers, and system users. | ## System Analyst Roles - Most large organizations now build project teams that incorporate several analysts with different but complementary roles. In smaller organizations, one person may play several of these roles. - The systems analyst role focuses on the IS ISSUES surrounding the system. - This person develops ideas and suggestions for ways that IT can support and improve business processes. - Helps design new business processes supported by IT. - Designs the new information system and ensures that all IS standards are maintained. ## Analyst Roles - The business analyst role focuses on the business issues surrounding the system. - This person helps to identify the business value that the system will create, develops ideas for improving the business processes, and helps design new business processes and policies. - The business analyst will have business training and experience. ## Analyst Roles - The requirements analyst role focuses on eliciting the requirements from the stakeholders associated with the new system. - As more organizations recognize the critical role that complete and accurate requirements play in the ultimate success of the system, this specialty has gradually evolved. - Requirements analysts understand the business well, are excellent communicators, and are highly skilled in an array of requirements elicitation techniques. ## Analyst Roles - The infrastructure analyst role focuses on technical issues surrounding the ways the system will interact with the organization's technical infrastructure (hardware, software, networks, and databases). - This person identifies infrastructure changes that will be needed to support the system. - The infrastructure analyst will have significant training and experience in networking, database administration, and various hardware and software products. - Over time, an experienced infrastructure analyst may assume the role of software architect, who takes a holistic view of the organization's entire IT environment and guides application design decisions within that context. ## Analyst Roles - The change management analyst role focuses on the people and management issues surrounding the system installation. - This person ensures that adequate documentation and support are available to users, provides user training on the new system, and develops strategies to overcome resistance to change. ## Analyst Roles - The project manager role ensures that the project is completed on time and within budget and that the system delivers the expected value to the organization. - The project manager is often a seasoned systems analyst who, through training and experience, has acquired specialized project management knowledge and skills. ## Analyst Roles - The roles and names used to describe them may vary from organization to organization. - In addition, there is no single typical career path through these professional roles. - Some people may enter the field as a more technically-oriented programmer/analyst. Others may enter as a business-oriented functional specialist with an interest in applying IT to solve business problems. ## Analyst Roles A diagram with two starting points: - Entry-level business function specialist - Entry-level programmer/analyst Both of these points lead to 5 different other roles: - Requirements analyst - Business analyst - Systems analyst - Infrastructure analyst - Project manager Some roles lead to other roles: - Project manager leads to Change management analyst - Infrastructure analyst leads to Software architect ## The Systems Development Life Cycle (SDLC) - In many ways, building an information system is like building a house. - First, the owner describes the vision for the house to the developer. - Second, this idea is transformed into sketches and drawings that are shown to the owner and refined (often, through several drawings, each improving on the other) until the owner agrees that the pictures depict what he or she wants. - Third, a set of detailed blueprints is developed that presents much more specific information about the house (e.g., the layout of rooms, placement of plumbing fixtures and electrical outlets, and so on). - Finally, the house is built following the blueprints and often with some changes and decisions made by the owner as the house is erected. ## SDLC A diagram with a light bulb starting point leading to 4 different boxes: - Planning - Analysis - Design - Implementation A thumbs up emoji represents system success at the end of the diagram. - Building an information system using the SDLC follows four fundamental phases: planning, analysis, design, and implementation. - Each phase is itself composed of a series of steps, which rely on techniques that produce deliverables (specific documents and files that explain various elements of the system). ## SDLC - SDLC is a process of gradual refinement. - The deliverables produced in the analysis phase provide a general idea what the new system will do. - These deliverables are used as input to the design phase, which then refines them to produce a set of deliverables that describes in much more detailed terms exactly how the system should be built. - These deliverables in turn are used in the implementation phase to guide the creation of the actual system. - Each phase refines and elaborates on the work done previously. ## 1-Planning - The planning phase is the fundamental process of understanding why an information system should be built and determining how the project team will go about building it. - It has two steps: - During project initiation - Once the project is approved ## 1-Planning - During project initiation, the system's business value to the organization is identified. How will it lower costs or increase revenues? - Most ideas for new systems come from outside the IS area (from the marketing department, accounting department, etc.) in the form of a system request. - A system request presents a summary of a business need, and it explains how a system that supports the need will create business value. - The IS department works together with the person or department generating the request (called the project sponsor) to conduct a feasibility analysis. ## Planning - The feasibility analysis examines key aspects of the proposed project: - The technical feasibility (Can we build it?) - The economic feasibility (Will it provide business value?) - The organizational feasibility (If we build it, will it be used?) - The system request and feasibility analysis are presented to an Information systems approval committee (sometimes called a steering committee), which decides whether the project should be undertaken. ## 1-Planning - Once the project is approved, it enters project management. - During project management, the project manager creates a work plan, staffs the project, and puts techniques in place to help the project team control and direct the project through the entire SDLC. - The deliverable for project management is a project plan that describes how the project team will go about developing the system. ## 2-Analysis - The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used. - During this phase, the project team investigates any current system(s), identifies improvement opportunities, and develops a concept for the new system. ## 2-Analysis 1. An analysis strategy is developed to guide the project team's efforts. Such a strategy usually includes a study of the current system (called the as-is system) and its problems, and envisioning ways to design a new system (called the to-be system). ## 2-Analysis 2. The next step is requirements gathering (e.g., through interviews, group workshops, or questionnaires). - The analysis of this information in conjunction with input from the project sponsor and many other people leads to the development of a concept for a new system. ## 2-Analysis - The system concept is then used as a basis to develop a set of business analysis models that describes how the business will operate if the new system were developed. - The set typically includes models that represent the data and processes necessary to support the underlying business process. ## 2-Analysis 3. The analyses, system concept, and models are combined into a document called the system proposal, which is presented to the project sponsor and other key decision makers (e.g., members of the approval committee) who will decide whether the project should continue to move forward. ## 2-Analysis - The system proposal is the initial deliverable that describes what business requirements the new system should meet. - Because it is really the first step in the design of the new system, some experts argue that it is inappropriate to use the term analysis as the name for this phase; some argue a better name would be analysis and initial design. ## Analysis - Because most organizations continue to use the name analysis for this phase, we will use it as well. - It is important to remember, that the deliverable from the analysis phase is both an analysis and a high-level initial design for the new system. ## Summary - System Analyst - System Analyst Skills - System Analyst Roles - System Development Life Cycle