Applied Systems Analysis Fall 2003 Douglas Low (315) 456-3372 (work) 2 min question (315) 703-6297 (home) 5 min question (315) 445-6044 (Lemoyne mailbox)

Slides:



Advertisements
Similar presentations
PROJECT RISK MANAGEMENT
Advertisements

System Integration Verification and Validation
Ossi Taipale, Lappeenranta University of Technology
Software Quality Assurance Plan
Systems Analysis and Design in a Changing World
Chapter 2 Analyzing the Business Case.
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
ITIL: Service Transition
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
W5HH Principle As applied to Software Projects
Systems Analysis and Design 9th Edition
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Chapter 2.
Lecture 13 Revision IMS Systems Analysis and Design.
1 Introduction to System Engineering G. Nacouzi ME 155B.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
Iterative development and The Unified process
Chapter 5: Project Scope Management
8 Systems Analysis and Design in a Changing World, Fifth Edition.
Problem Areas with the Project Class Descriptions were non existent Use case descriptions were terse or non existent Verification methods were wrong Equal.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Configuration Management
Project Scope Management
What is Business Analysis Planning & Monitoring?
S/W Project Management
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Chapter 8: Systems analysis and design
The Differences Between the Project Manager and the Systems Engineer Kasse Tim Kasse Kasse Initiatives LLC +1 – USA +49 (0)
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Software Requirements Engineering CSE 305 Lecture-2.
A GENERIC PROCESS FOR REQUIREMENTS ENGINEERING Chapter 2 1 These slides are prepared by Enas Naffar to be used in Software requirements course - Philadelphia.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
IT Requirements Management Balancing Needs and Expectations.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
SacProNet An Overview of Project Management Techniques.
Project Life Cycle – Project Initiation © Ed Green Penn State University All Rights Reserved.
Lecture 7: Requirements Engineering
Introduction Project Management. Projects A unique process, consisting of a set of coordinated and controlled activities with start and finish dates,
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Network design Topic 6 Testing and documentation.
1 IT Project Management, Project Failure and Success  Introduction  Projects operate in a broad organizational environment.  Project managers need to.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Information Technology Project Management, Seventh Edition.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
Systems Analysis and Design in a Changing World, Fifth Edition
ITIL: Service Transition
Chapter 4: Business Process and Functional Modeling, continued
Project Management Processes
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
Software Requirements
Project Management Process Groups
Project Management Processes
Engineering Processes
Introduction to Project Management
Presentation transcript:

Applied Systems Analysis Fall 2003 Douglas Low (315) (work) 2 min question (315) (home) 5 min question (315) (Lemoyne mailbox) leave message Class Notes 1

Problem Areas with the Project Class Descriptions were non existent Use case descriptions were terse or non existent Verification methods were wrong Equal effort within teams

Grading Example Possible # of points Change Was 11% Penalty points

Grades 88%104%88%92%86%95% 0% - not started 75% - late Average was 89.7 ( not counting the 0%)

Class Descriptions Class Descriptions should introduce the reader to the object class It should be a paragraph It should denote What are the responsibilities of the class If it is a hardware, software, person, parameter … etc If it is a commercial product IF it is temporary, permanent Part of another class (aggregation composition) Anything else that you know about the class/ object

Use Case Descriptions Use case descriptions should describe what the use case is doing and who is doing it. It should: Indicate the goal of the Use Case. e.g. Indicate the scope and duration of the use case. This use case creates a valid order based on customer provided information. It is executed whenever the customer indicates a desire to finalize the order. Since the information is private, this session is done in a secure mode. The entire process of entering an order is temporary and is aborted if the customer does not respond within a proper time frame. All the order and customer information derived from this use case is stored in a secure server. The process ends whenever all the information is collected and the customer indicates finished, the customer cancels the order, or the process times out from lack of activity.

Requirements Verification Methods Most requirements should be tested. Test : The system is run in a particular sequence to show the successful implementation of the requirement. The test must match the documented expected test results. Demonstrate : While similar to test the requirement is shown to be correct. The result must be obvious. ( visible, audible… ) It must be difficult to attach a test result. Inspect : Static characteristic shown to the customer. Analyze : Some type of analysis is performed and documented. This could be a spreadsheet, simulation… the documentation must be captured in a formal paper.

Equal Effort Among Members Within Teams Next Time I will ask each member of a team to rate the other members within the team This will affect the team member’s individual grades.

Trade Study Purpose Purpose : Trade study is used to objectively choose between multiple acceptable candidate solutions Halloween Party

Trade Study Description select the best solution to meet an identified problem within defined constraints Defines a structured analytic framework for evaluating a set of alternative concepts, designs, or components Conducted concurrently with other requirements development and design activities Range from an informal comparison of alternatives to major efforts using sophisticated computer tools for simulation and cost estimation. ? What Costume should I wear? Who should I go with?

Trade Study Process Define ObjectivesDefine Objectives Identify CandidatesIdentify Candidates Establish Evaluation CriteriaEstablish Evaluation Criteria Conduct analysisConduct analysis Document ResultsDocument Results ReviewReview

Stakeholders can be: Other business disciplinesOther business disciplines CustomerCustomer CorporateCorporate YourselfYourself Etc.Etc. Define Objective for Analysis Define the objective and purpose of the analysis Determine scope of trade study Determine level of supporting analyses Determine amount of review and approvals needed Determine level of documentation Obtain approval with stakeholders of the objective and ensure that there is agreement on the purpose and scope of the analysis

Define Objective for Analysis - Example Objective: Decide where best to eat lunch on a typical workday. Purpose: Get the best value for lunch Scope: Where, how, what, how much, with whom Be sure to get approval of the purpose and scope of the objective from stakeholders.

Establish Evaluation Criteria and Weights Establish an evaluation criteria and weighting for considering system design alternatives that includes, as a minimum, cost drivers, total ownership and life cycle cost, complexity, technical limitations, environmental impact, system expansion, growth, and risk. Establish an evaluation criteria and weighting that is a tailored version of the standard criteria and weighting Review the evaluation criteria to ensure that they are consistent with the range of alternatives. Obtain agreement of decision maker on evaluation criteria and weights

Weighting Tailor criteria and weighting as appropriate. Ensure weighting is normalized, and grading uses the same scale (good=low) and range across criteria. Tailor criteria and weighting as appropriate. Ensure weighting is normalized, and grading uses the same scale (good=low) and range across criteria.

Establish Evaluation Criteria and Weights - Example Most Trade Studies will have items related to Cost, Schedule, and Performance and Risk as part of their evaluation criteria. Refer to SYSENG-100 Appendix E criteria weights

Establish Evaluation Criteria and Weights - Example Grades for “Time Required” 0 to 15 minutesVery low impact (1) 15 to 30 minutesLow impact (2) 30 to 45 minutesMedium impact (3) 45 to 60 minutesHigh impact (4) Over 60 minutesVery high impact (5)

Identify Candidate Alternatives Generate alternative candidate solutions. Reject unfeasible alternatives Document rejected candidates Feedback loop Option 1 Option 2 Option n... Option 3

Identify Candidate Alternatives - Example alternatives For larger trade studies, it is a good idea to have a formal review of alternatives and criteria before proceeding with the analysis.

Conduct Analysis of Alternatives Develop timelines scenarios for system operation and user interaction for each system design alternative. Allocate key requirements to the hardware and software components for each of the design alternative as a part of the analysis. Analyze all candidate alternatives that have been identified. Analyze the alternatives using a structured decision making technique that is appropriate for the analysis. Use the evaluation criteria and weighting to select the recommended alternative (see example). Determine the alternative representing the “Best Value” for projects that have a CAIV requirement. Evaluate the failure conditions associated with each of the alternatives. Perform a sensitivity analysis to determine if any factors inordinately dominate the selection outcome

Conduct Analysis of Alternatives - Example 1 Example: Timeline Analysis Use analysis techniques such as timeline analysis, CAIV, analysis of possible failure conditions, etc.

Conduct Analysis of Alternatives - Example 2 Another Example: Data Gathering McDonald’s Web Site

Conduct Analysis of Alternatives - Example 3 Apply weights to grades to find optimum alternative Multiply weight times grade, and sum across all criteria, i.e..3(1)+.3(1)+.3(1)+.1(3) =1.2

Document Analysis Results The report contains the following: Document the rationale for the analysis decisions. Document the decision making technique used for the analysis and the rationale for its selection. Document the rationale for the selection of the evaluation criteria and weighting for the analysis. Document alternatives considered and the rationale for not selecting them as the recommended alternative. It is recommend to produce the document incrementally in parallel with the process

Document Analysis Results - Styleguide 1Introduction 2Applicable Documents 3Trade Study Analysis 3.1Trade Study Objective 3.2Requirements, Constraints, and Assumptions 3.3Evaluation Criteria, Grading, Weighting and Scoring 3.4Definition of Alternatives 3.5Analysis of Alternatives 3.6Summary of Analysis 4Conclusions and Recommendations

Document Analysis Results - Example Trade Study Report Style-guide

Review/Approve Analysis Report Review the assumptions to ensure that they are reasonable and valid for the alternatives being considered. Review the selected alternative to ensure it is the best solution based on the evaluation criteria and weighting. Review the candidate alternatives to ensure that the appropriate alternatives have been analyzed. If all appropriate alternatives have not been analyzed, then the analysis of alternatives needs to be continued

Trade Studies are usually conducted to help understand competing solutions and to select the most optimal solution. Trade Studies are usually conducted for items significantly impacting: Cost Schedule High Risk Items Performance Objectives Architectural Design When to Conduct a Trade Study

Example Spreadsheet

Homework : Due November 3rd Divide up your project classes among team members. Create class descriptions. Divide up your project use cases among team members. Create / re-do use case descriptions. Divide up requirements among team membersDivide up your project classes among team members. Create class descriptions. Divide up your project use cases among team members. Create / re-do use case descriptions. Divide up requirements among team members Send them to me ( subject: Project updates)Send them to me ( subject: Project updates) Add them to your project (don’t send them to me)Add them to your project (don’t send them to me) Read Feasibility Analysis (chapter 10) of WhittenRead Feasibility Analysis (chapter 10) of Whitten Do a trade study with 3 – 4 alternative candidatesDo a trade study with 3 – 4 alternative candidates No class on October 27, 2003