XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.

Slides:



Advertisements
Similar presentations
IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner.
Advertisements

Systems Development Environment
Session # 49 Software Development Lifecycle for Business People Holly Hyland Jim McMahon.
Chapter 1 The Systems Development Environment
Ch 3 System Development Environment
1 The Database Application Development Process The Database Application Development Process.
Rational Tool Overview. Introduction Requirements-Driven Software Development with Rational Analyst Studio. Tafadzwa Nzara Analysis & Design Consultant.
Rational Unified Process
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Requirements Specification
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
CATEGORIES OF INFORMATION There are three main categories of business information,and these are related to the purpose for which the information is utilized.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
Chapter 1 The Systems Development Environment
Unit Five – Transforming Organizations
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
CHAPTER 17 Building Software to Support an Agile Organization
Mastering OOA/OOD with UML. Contents Introduction Requirements Overview OOAOOD.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Chapter 1 The Systems Development Environment
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
Chapter 1 The Systems Development Environment
Business Analyst Training in Chennai Business Analyst Training in Chennai Spark Training Academy.
Systems Analysis and Design: The Big Picture
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
RUP Requirements RUP Artifacts and Deliverables
UML - Development Process 1 Software Development Process Using UML (2)
Introduction to Software Quality Assurance (SQA)
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
Chapter 2 The process Process, Methods, and Tools
Chapter 1 The Systems Development Environment
Appendix D McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers Unit 11 Slide 1 Chapter 1 The Systems Development Environment.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
The Systems Development Methodologies. Objectives  Describe the information Systems Development Life Cycle (SDLC)  Explain prototyping  Explain Rapid.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 4 Slide 1 Chapter 1 The Systems Development Environment.
1 Configuration Management “The Cookbook Approach”
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Foundations of Geospatial System Development II Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
© 2005 by Prentice Hall Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
Business Analysis Healthcare Domain Classroom & Online Training Mail Id : Skype Id : info.vibloo US: IND:
The principles of an object oriented software development process Week 04 1.
The Systems Development Environment Systems Analysis and Design II.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
11 ADM2372 Management Information Systems (MIS) Chapter 10 – Part I Systems Development Chapter 10 – Part I Systems Development.
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
Systems Development Process and Methodologies Dr. T. Ravichandran.
Software Engineering cosc 4359 Spring 2017.
Chapter 1 The Systems Development Environment
Chapter 2 The Systems Development Environment
Chapter 1 The Systems Development Environment
Introduction to Software Engineering
Rational Unified Process
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Presentation transcript:

XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle Copyright 2000 Claire N. Streb

XXX, Inc. 2 Technical Capabilities REQUIREMENTS ENGINEERING (RE) A process that establishes and maintains agreement between the customer and the project team on the changing requirements of the system Picture is copyright 2000 Claire N. Streb

XXX, Inc. 3 Technical Capabilities Relative Cost to Repair User Input.1-.2 Design 0.5 Coding 1 Unit Test 2 Acceptance Test 5 Maintenance 20 RE -- Why? Picture is from Rational Corporation

XXX, Inc. 4 Technical Capabilities RE -- Who? Analysts Tech writers & docs Corp Mgmt. Dev. Mgrs & Proj. Mgrs QA & Test Requirements Developers & Designers Users Picture is from Rational Corporation

XXX, Inc. 5 Technical Capabilities RE -- What?  Analyze the Problem  Understand Stakeholder Needs  Define the System  Manage the System Scope  Manage Changing Requirements RE -- What?  Analyze the Problem  Understand Stakeholder Needs  Define the System  Manage the System Scope  Manage Changing Requirements

XXX, Inc. 6 Technical Capabilities RE -- Needs Analysis  Analyze the problem and identify stakeholder needs (features) interviews questionnaires brainstorming sessions (JAR/JAD) storyboards prototypes  Capture results in a Vision Document RE -- Needs Analysis  Analyze the problem and identify stakeholder needs (features) interviews questionnaires brainstorming sessions (JAR/JAD) storyboards prototypes  Capture results in a Vision Document

XXX, Inc. 7 Technical Capabilities RE -- Needs Analysis -- XXX Cust. Svc.  Business-to-Business (B2B) Warranty claims On-line manuals Diagnostics Invoicing w/tracking and credits Data warehouse On-line ordering RE -- Needs Analysis -- XXX Cust. Svc.  Business-to-Business (B2B) Warranty claims On-line manuals Diagnostics Invoicing w/tracking and credits Data warehouse On-line ordering

XXX, Inc. 8 Technical Capabilities RE -- Detailed Analysis  Specify software requirements by defining use cases and actors  Define requirement attributes  Capture results in a: Document (Narrative) Model (Diagram, such as UML) Tool (such as RequisitePro*) * RE -- Detailed Analysis  Specify software requirements by defining use cases and actors  Define requirement attributes  Capture results in a: Document (Narrative) Model (Diagram, such as UML) Tool (such as RequisitePro*) *

XXX, Inc. 9 Technical Capabilities RE -- Detailed Analysis Sample Use Case Diagram RE -- Detailed Analysis Sample Use Case Diagram Picture is from Rational Corporation

XXX, Inc. 10 Technical Capabilities ANALYSIS AND DESIGN  Define the Architecture and Infrastructure  Analyze System Behavior  Design the Database  Design Components  Capture results in a Model (such as Rose) ANALYSIS AND DESIGN  Define the Architecture and Infrastructure  Analyze System Behavior  Design the Database  Design Components  Capture results in a Model (such as Rose)

XXX, Inc. 11 Technical Capabilities ANALYSIS AND DESIGN -- Architecture / Distribution Patterns / Infrastructure Picture is from Rational Corporation

XXX, Inc. 12 Technical Capabilities ANALYSIS AND DESIGN-- Analyze System Behavior  Perform Use Case Analysis to transform the behavioral descriptions in the use cases into a set of elements upon which the design can be based ANALYSIS AND DESIGN-- Analyze System Behavior  Perform Use Case Analysis to transform the behavioral descriptions in the use cases into a set of elements upon which the design can be based

XXX, Inc. 13 Technical Capabilities ANALYSIS AND DESIGN-- Design the Database and Components  Define the Persistent Mechanisms  Refine the Design Elements ANALYSIS AND DESIGN-- Design the Database and Components  Define the Persistent Mechanisms  Refine the Design Elements

XXX, Inc. 14 Technical Capabilities IMPLEMENTATION / DEVELOPMENT  Implement the Design  Code Reviews  Software Configuration Management  Unit Tests  Integration Tests IMPLEMENTATION / DEVELOPMENT  Implement the Design  Code Reviews  Software Configuration Management  Unit Tests  Integration Tests

XXX, Inc. 15 Technical Capabilities QUALITY ASSURANCE  Process Improvement and Validation  Verification and Validation  Auditing QUALITY ASSURANCE  Process Improvement and Validation  Verification and Validation  Auditing

XXX, Inc. 16 Technical Capabilities QA -- Process Improvement and Validation  Develop Plans Protocols Procedures  Assess and Analyze  Strategize QA -- Process Improvement and Validation  Develop Plans Protocols Procedures  Assess and Analyze  Strategize

XXX, Inc. 17 Technical Capabilities QA -- Verification and Validation  Requirements  Design  Code  Testing  Data  Product Integrity QA -- Verification and Validation  Requirements  Design  Code  Testing  Data  Product Integrity

XXX, Inc. 18 Technical Capabilities QA -- Testing  According to the Standard: Test Plans, Procedures, and Reporting  Automated Testing Experience  Specialized Domain Expertise Medical, Document Publishing, etc.  Tools: Rational Test Studio QA -- Testing  According to the Standard: Test Plans, Procedures, and Reporting  Automated Testing Experience  Specialized Domain Expertise Medical, Document Publishing, etc.  Tools: Rational Test Studio

XXX, Inc. 19 Technical Capabilities QA -- Auditing  ISO 9001 Quality System Standard  FDA Quality System Regulation  Good Manufacturing Practice (GMP)  Capability Maturity Model (CMM)  IEEE Software Engineering Standards QA -- Auditing  ISO 9001 Quality System Standard  FDA Quality System Regulation  Good Manufacturing Practice (GMP)  Capability Maturity Model (CMM)  IEEE Software Engineering Standards

XXX, Inc. 20 Technical Capabilities PROJECT LIFE CYCLE -- Development Methodologies  Traditional (Waterfall)  RUP - Rational Unified Process  RAD - Rapid Application Development  XP - Extreme Programming PROJECT LIFE CYCLE -- Development Methodologies  Traditional (Waterfall)  RUP - Rational Unified Process  RAD - Rapid Application Development  XP - Extreme Programming

XXX, Inc. 21 RTE Technical Capabilities Project Life Cycle -- Iterative Development

XXX, Inc. 22 Technical Capabilities Next Steps  Study XXX’s Needs Analysis Model  Study XXX’s Architecture  Recommend Toolset  Begin Requirements Engineering  Begin Development Planning  Begin Test Environment Planning Next Steps  Study XXX’s Needs Analysis Model  Study XXX’s Architecture  Recommend Toolset  Begin Requirements Engineering  Begin Development Planning  Begin Test Environment Planning