Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Course: e-Governance Project Lifecycle Day 1
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
More CMM Part Two : Details.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
© ABB AB, Corporate Research - 1 5/19/2015 abb Project Breakdown Structure Creation.
Iterative Process Planning
Rational Unified Process
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Software Engineering.
Software Project Transition Planning
CS 501: Software Engineering
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Software Configuration Management (SCM)
Iterative development and The Unified process
Project Management Methodology (PMM)
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Engineering Institute Capability Maturity Model (CMM)
Chapter 6– Artifacts of the process
S/W Project Management
CPTE 209 Software Engineering Summary and Review.
UML - Development Process 1 Software Development Process Using UML (2)
Sixteenth Meeting 6:30 – 9:20 pm, Thursday, September 20, 2001 Review - Looking Forward (from Part IV, Chapter 15 of Royce’ book) Final Examination.
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,
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
Fifteenth Lecture Hour 10:30 – 11:20 am, Sunday, September 16 Tailoring the Process (from Chapter 14 of Royce’ book)
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Fourteenth Lecture Hour 9:30 – 10:20 am, Sunday, September 16 Software Management Disciplines Project Control and Process Automation (from Part III, Chapter.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Software Engineering Management Lecture 1 The Software Process.
Chapter – 9 Checkpoints of the process
Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Second Hour Lecture 9:30 – 10:20 am, September 8, 2001 Evolution of Software Economics Improving Software Economics (from Chapters 2 and 3 of Royce’ book)
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 8 Workflows of the Process Taken from Walker Royce’s textbook – Software Project Management plus a number of Personal Comments.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
The Goal: To Climb Above The Competition Copyright 2005: I Lead Projects, L.L.C. Course Description Project Process Workplates Project Process Workplates.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Engineering Lecture 9: Configuration Management.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Pragmatics 4 Hours.
Software Engineering Management
Object Oriented Analysis and Design
Rational Unified Process
Presentation transcript:

Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

Topics for Today Artifact Sets Management Artifacts Engineering Artifacts Pragmatic Artifacts

Review - Phases of the Life-cycle Process

Overview of the Artifact Sets

The Five Artifact Sets Requirements Set Design Set Implementation Set Deployment Set Management Set

Captures “contracts” among project personnel. –Management, architects, designers, testers, marketers, administrators, …. –Funding authorities, other management, regulators, customers, … Contains plans, resource requirements, budgets, costs, schedules, milestones, releases, ……

Requirements Set Forms the basis for evaluating the other three engineering artifact sets (design, implementation, deployment sets). Forms the basis for test cases.

Design Set Contain –Design model –Test model –Architecture description Future automation should support: –Complexity analysis –Style analysis –Consistency analysis

Implementation Set Contains –Source code –Executables for stand-alone testing –Custom components –Application program interfaces –Data files

Deployment Set Contains –User deliverables –Executable code –Target-specific data –Run-time files –User manual

Artifact Set Tools Management Set tools. –Scheduling, work flow, defect tracking, change management, documentation, resource management, presentation tools. Requirements Set tools. –Requirements management tools. Design Set tools. –Visual modeling tools. Implementation Set tools. –Compiler/debugger tools, code analysis tools, test coverage analysis tools, and test management tool. Deployment Set tools. –Test automation tools, network management, commercial components (operating systems, GUI’s DBMS’s, networks, middleware, and installation tools.

Life-cycle Focus on Artifact Sets

Life-cycle Evolution of the Sets

Management Artifacts Work Breakdown Structure (WBS) Business Case –Transforms the vision into economic terms. Release Specifications –Includes evaluation criteria for intermediate and final releases. Software Development Plan (SDP) –Schedules, releases, processes, resources, environments, organization, key personnel, manning, change management, quality control, standards and procedures.

Management Artifacts (cont’d) Release Descriptions –Functions, performance evaluations, test results, issues, follow-up action needs. Status Assessments –Include review of resources, personnel/staffing actions, financial data, top issues, action items, technical progress, major milestone plans and results, customer issues, look-ahead.

Management Artifacts (cont’d) Software Change Orders Software Problem Reports and Tracking Deployment Document –Transition plans, marketing plans, sales plans, and training course plans. Environment –Defines the development and maintenance environments. Includes requirements management, visual modeling, document automation, host and target programming tools, automated regression testing, integrated change management and defect tracking.

Artifact Sequences

Engineering Artifacts Vision Document –The source for capturing the expectations among stakeholders. –Written from the users’ perspective. –Focus is on essential features of the system, and the acceptable levels of quality. –Includes the operational concept. Architecture Description Software Users Manual –Contains installation procedures, usage procedures and guidance, operational constraints, and a user interface description. –Written by the test team.

Artifacts Summary Artifacts of modern software development may be divided into five sets –Management, Requirements, Design, Implementation and Deployment. Emphasis changes from the Engineering Stage to the Production Stage, but all artifacts should evolve as work progresses. Artifacts provide the basis for managing development of the products of the software project.

Assignment for Next Class Read Chapter 6 of Royce’ book, on artifacts of the process. –Learn the names of the five artifact sets for modern software management. –Learn the nine elements of the management artifact set. Read Chapter 8, “Calling the Shot” of Brooks’ book. If assigned to you, prepare the “Brooks’ Chapter 8” 20 minute report (for presentation to the class).