SA Lecture 1 Introduction BA.pdf

System Analysis and Design Lecture 1 Course ILOs Analyze the business needs for information and to develop an appropriate strategy to provide the required information service. Use various information gathering techniques for eliciting user information requirements and system expec...

System Analysis and Design Lecture 1 Course ILOs Analyze the business needs for information and to develop an appropriate strategy to provide the required information service. Use various information gathering techniques for eliciting user information requirements and system expectations. Construct and interpret a variety of system analysis and design models including UML diagrams and structured models. Produce the required systems documentation including project plan at each point in the analysis and design of an information system. Design an effective graphical user interface and apply the general guidelines for assessing the system usability. Differentiate and evaluate testing, installation, configuration and maintenance strategies. 2 Course Content Introduction to Business Analysis Basic Concepts Analysis Phase Requirement Determination steps (Requirement Elicitation Techniques) Requirement Structuring Requirement life cycle and traceability Process Modeling Design Phase Program Design Interface Design Test Case Design Installation and Maintenance 3 Systems Development Life Cycle (SDLC) Traditional methodology for developing and maintaining information systems Orderly set of activities conducted and planned for each development project. Each phase has specific outcomes and deliverables that feed important information to other phases Phases in SDLC: 1. Planning 4. Implementation 2. Analysis 5. Maintenance 3. Design Output: Software Documentation about the system and how it was developed Standard and Evolutionary Views of SDLC  SDLC Planning Phase - Why Information system should be built. (need) - How the project team will go building it. (plan) 1 Project Initiation: - Business needs and how the system create a business value. - Feasibility Analysis. 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?) 2 Once Approved, Project Management. Project manager creates a work plan, staffs the project, techniques. - Deliverable: Project Plan  SDLC Analysis Phase - Who will use the system. - What the system will do. - Where and when it will be used. Two Sub phases: Study and structure 1- Requirements Determination: system requirements Careful study of organization current procedures and the information systems used to perform organizational tasks. 2- Requirements Structuring Relationships between requirements and eliminating redundancy  SDLC Design Phase - Convert recommended solution to system specifications. - How the system will operate in terms of the hardware, software, and network infrastructure, the user interface, forms, and reports, specific programs, databases, and files. SDLC Implementation Phase Code, validate, install, and support the information system SDLC Maintenance Phase Systematically repair and improve the information system. - Maintenance is not a separate phase but a repetition of the other life cycle phases The Heart of the Systems Development Process Basic Concepts of Business Analysis What is Business Analysis? Business analysis is the practice of enabling change in an enterprise by defining business needs and recommending solutions that deliver value to stakeholders. Business analysis enables an enterprise to articulate needs and the rationale for change, and to design and describe solutions that can deliver value. Business analysis may be performed within the boundaries of a project or throughout enterprise evolution and continuous improvement. Who is a Business Analyst? A business analyst is any person who performs business analysis tasks no matter their job title or organizational role. Business analysts are responsible for discovering and analyzing information from a variety of sources within an enterprise, including tools, processes, documentation, and stakeholders. The business analyst is responsible for eliciting the actual needs of stakeholders—which frequently involves investigating and clarifying their expressed desires—in order to determine underlying issues and causes. Who is a Business Analyst? (cont.) Business analysts play a role in aligning the designed and delivered solutions with the needs of stakeholders. The activities that business analysts perform include: understanding enterprise problems and goals analyzing business needs and solutions devising strategies driving change facilitating stakeholder collaboration business architect business systems analyst data analyst enterprise analyst management consultant process analyst product manager product owner requirements engineer systems analyst System Analyst? 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. Systems analysts may perform the following activities: - identify the organizational improvements )settled by business analyst) - design systems to cope those improvements - train others to use the systems. System Analyst skills can be broken down into six major categories: technical, business, analytical, interpersonal, management, and ethical. Business Analyst vs. System Analyst Business Analyst System Analyst more business focused on the business more technically focused on the technical process side. side. Where a business analyst might work on systems analysts only come in when there is something that doesn’t actually involve a a software change. software change because they just might fix the business process. they’re focused more in on the software aspect of the solution. They might be doing more data modeling, more data design, how does data move between systems, how are the systems connected, working and integrated together to meet a feature. System Analyst & SDLC Produce a plan for the proposed project that the team will follow through the SDLC. System Analyst & SDLC - Do requirement Gathering and structuring. -The analyst thoroughly studies the organization’s current procedures and the information systems used to perform the organizational tasks.  System Analyst & SDLC - convert the description of the recommended alternative solution into logical and then physical system specifications. - design all aspects of the system, from input and output screens to reports, databases, and computer processes. - provide the physical specifications of the system they have designed, either as a model or as detailed documentation.  System Analyst & SDLC - Turn system specifications into a working system that is tested and then put into use. - During testing, analysts help in testing individual programs and the entire system in order to find and correct errors.  System Analyst & SDLC - Systematically repair and improve the information system The Business Analysis Core Concept Model The Business Analysis Core Concept Model Core Concept Description Need - A problem or opportunity to be addressed. - Needs can cause changes by motivating stakeholders to act. Change - The act of transformation in response to a need. - Change works to improve the performance of an enterprise.  The Business Analysis Core Concept Model Core Description Concept Solution - A specific way of satisfying one or more needs in a context. - A solution satisfies a need by resolving a problem faced by stakeholders or enabling stakeholders to take advantage of an opportunity. Stakeholder - A group or individual with a relationship to the change, the need, or the solution. - Stakeholders are often defined in terms of interest in, impact on, and influence over the change. - Stakeholders are grouped based on their relationship to the needs, changes, and solutions. Stakeholder A stakeholder is an individual or group that a business analyst is likely to interact with directly or indirectly. The generic list of stakeholders includes the following roles: customer end user project manager sponsor supplier  The Business Analysis Core Concept Model Value The worth, importance, or usefulness of something to a stakeholder within a context. Value can be in the form of losses, risks, and costs. Value can be tangible or intangible. A - Tangible value is directly measurable. Tangible value often has a significant monetary component. B- Intangible value is measured indirectly. Intangible value often has a significant motivational component, such as a company's reputation or employee morale. The Business Analysis Core Concept Model Core Concept Description Context - The circumstances that influence, are influenced by, and provide understanding of the change. - Changes occur within a context. The context is everything relevant to the change that is within the environment. - Context may include attitudes, behaviors, beliefs, competitors, culture, demographics, goals, governments, infrastructure, languages, losses, processes, products, projects, sales, seasons, terminology, technology, weather, and any other element meeting the definition.  Computer-Aided Software Engineering (CASE) 30 CASE Tools Computer-Aided Software Engineering (CASE) CASE tools are used to support a wide variety of SDLC activities. CASE tools can be used to help in multiple phases of the SDLC: project initiation and planning, analysis, design, implementation and maintenance. Example products: Oracle Designer, Rational Rose CASE Tools (cont.) Diagramming tools enable system analysts to represent the system graphically (draw diagrams). Computer display and report generators help prototype how systems “look and feel.” Analysis tools automatically check for incomplete, inconsistent, or incorrect specifications in diagrams, forms, and reports. Documentation generators produce technical and user documentation in standard formats. Code generators enable the automatic generation of program and database definition code directly from the design documents, diagrams, forms, and reports. 32 CASE Tools (cont.) 33 Sources of Application Software 34 Outsourcing Turning over responsibility of some or all of an organization's information systems applications and operations to an outside firm. Reasons to outsource Cost-effective Free up internal resources Reduce time to market System development is a non-core activity for the organization Sources of Application Software Sources of Application Software Microsoft Oracle Sources of Application Software Accounting, HR, Manufacturing, Supply Chain (Shared Database) Sources of Application Software Google Apps Salesforce.com (CRM) Sources of Application Software Linux OS MySQL database system Firefox web browser SourceForge.net Thank You 48