How Systems are Developed The Commercial Life Cycle Model Common form of the Software Life Cycle Used through the commercial, industrial, institutional.

Slides:



Advertisements
Similar presentations
DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Advertisements

SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
Define & Compare Flowcharts of Each Method Tom Delong.
ITIL: Service Transition
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 4 th Ed Chapter Software Development Software Life Cycle UML Diagrams.
School of Computing, Dublin Institute of Technology.
Unit 191 Introduction to Software Engineering The objective of this section is to introduce the subject of software engineering. When you have read this.
Illinois Institute of Technology
Configuration Management
Software Engineering CSE470: Systems Engineering 35 Computer System Engineering Computer System Engineering is a problem-solving activity. Itemize desired.
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
Software System Integration
Trigger and online software Simon George & Reiner Hauser T/DAQ Phase 1 IDR.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
"In the name of ALLAH, most Gracious, most Compassionate".
CEN 4935 Senior Software Engineering Project Joe Voelmle.
Effective Methods for Software and Systems Integration
Systems Analysis And Design © Systems Analysis And Design © V. Rajaraman MODULE 14 CASE TOOLS Learning Units 14.1 CASE tools and their importance 14.2.
Chapter 8 : Software Quality Assurance Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
Software Configuration Management
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 1.
INT-Evry (Masters IT– Soft Eng)IntegrationTesting.1 (OO) Integration Testing What: Integration testing is a phase of software testing in which.
Configuration Management (CM)
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
CASE Tools Union Palenshus. In the early days… ► Software engineering tools consisted solely of translators, compilers, assemblers, linkers, loaders,
Fundamentals of Information Systems, Second Edition 1 Systems Development.
ANKITHA CHOWDARY GARAPATI
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
Software Engineering Lecture # 1.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
Chapter 7 Implementation. Implementation Approaches F Big bang –Code entire system and test in an unstructured manner F Top-down –Start by implementing.
CSC 480 Software Engineering Test Planning. Test Cases and Test Plans A test case is an explicit set of instructions designed to detect a particular class.
MNP1163/MANP1163 (Software Construction).  Minimizing complexity  Anticipating change  Constructing for verification  Reuse  Standards in software.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
UML (Unified Modeling Language)
What is a level of test?  Defined by a given Environment  Environment is a collection of people, hard ware, software, interfaces, data etc.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
DETAILED DESIGN, IMPLEMENTATION AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Integrating the Code during the Development Alexander Vakrilov Telerik Corporation
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Barron’s chapter 5 Software development life cycle.
IFS310: Module 9 Systems Design - Procurement Phase - Software Design.
Software Engineering Zhang Shuang
OBJECT ORIENTED VS STRUCTURED WHICH ONE IS YOUR CHOICE.
ITIL: Service Transition
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
How Systems are Developed
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Software Quality Assurance (SQA)
IEEE Std 1074: Standard for Software Lifecycle
EIN 6133 Enterprise Engineering
CHAPTER 2 Testing Throughout the Software Life Cycle
Software System Integration
Static Testing Static testing refers to testing that takes place without Execution - examining and reviewing it. Dynamic Testing Dynamic testing is what.
Instrument PDR Summary of Objectives
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Logical Architecture & UML Package Diagrams
Presentation transcript:

How Systems are Developed The Commercial Life Cycle Model Common form of the Software Life Cycle Used through the commercial, industrial, institutional government communities University of Houston Clear Lake Science and Computer Engineering James C. Helm, Ph.D.,P.E. Engineering Division Chair

Example Software Development Process This process illustrates the major steps and flow that might be typical of a DoD or major Government Contractor. The documents would be obtained from the DoD standard, MIL-STDs, or IEEE NASA Software Document Standard, Software Engineering Program, NASA- STD

Requirement Phase Deals with all kinds of requirements –system –software –hardware –human system Interface –human in the loop

Design Phase Normally consists of two parts –Preliminary Design –Detailed Design

Code Phase Implements the detailed design –Some form of programming language –Three possible coding options top-down bottom-up middle-out

Select Appropriate Compiler/ Assembler Select Appropriate Programming Support Environment Initiate Appropriate Controls Follow Standards & Conventions Establish Software Library Establish/ Retain Required Databases FROM DESIGN PHASE Develop Large Driver to Stimulate System Code Top Level CSC Then Next Level, etc. Final Integration is minimal Test Whole System Each Time TOP-DOWN Develop Several Drivers to Stimulate Subsystems Code CSCs as functional threads Integration is moderate throughout Test Each Functional Thread MIDDLE-OUT Develop many drivers to Stimulate CSUs Code CSUs separately Integration is Time Consuming Test Each CSU Extensively BOTTOM-UP Determine Optimum Coding Strategy & Sequence OPTION 2 OPTION 3 OPTION 1 Ready for I & t

Correlation Between Specifications and Test Match the kind of software being developed and the manner in which it is being implemented and integrated –Specification hierarchy –Test hierarchy

Integration and Testing Phase Major Activities shown on next slide Determine early the selection and specification of the optimum test strategy Select: tools, instrumentation, recording methods and SW drivers Select environment: hardware configuration and location of tests