Copyright ⓒ 2005 SE Technology. Co.,Ltd. All rights reserved. What are the differences between the architectural description of large scale software development.

Slides:



Advertisements
Similar presentations
Copyright Clarion Consulting 2007 Clarion Consulting Project Management Practices in Irish Organisations Dublin September 12 th, 2007.
Advertisements

Jeremy S. Bradbury, James R. Cordy, Juergen Dingel, Michel Wermelinger
System Integration Verification and Validation
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
The Chaos Report © The Standish Group 1995.
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)
Prepared By: Certified Compliance Solutions, Inc. August 2012
Hardware/Software Integration in System-of-Systems Architecting: The Role of Systems Modeling University of Southern California Viterbi School of Engineering.
9-Jun-15 GCIS 504/GENG 580- The requirements problem1.
SWE Introduction to Software Engineering
Software and System Engineering Integration Sponsor Overview Kristen Baldwin Deputy Director, Software Engineering and System Assurance Office of the Under.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
The Use of Zachman Framework Primitives for Enterprise Modeling
Requirements Specifications Today: Homework #1 due For next class: Pressman 11; SRD Team Status Reports Requirements Process (continued) Bio Break ( 5.
SE 555 – Software Requirements & Specifications Introduction
Software Quality Assurance. CS351 - Software Engineering (AY2004)2 Software engineering processes Systems vs. Software –Terms often used interchangeably.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Introduction to Software Quality Assurance (SQA)
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Software Engineering Week 9 – Brief Introduction of Requirement #1 A.A. Gde Bagus Ariana, S.T.
The Challenge of IT-Business Alignment
Reducing ITS Project Risk By using and developing consensus based regional ITS architecture and a systems engineering process Robert S. Jaffe, Ph.D., CSEP.
Dr. Tom WayCSC Software Requirements CSC 4700 Software Engineering Lecture 2 Based on Sommerville, Chapter 6.
Ch.1 1 Software Engineering A Preview Chapter 1. Ch.1 2 Outline My Background Definitions of software engineering (SE) Historical origins of SE SE as.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
The Architecture Lecture September 2006 Cem Kaner CSE 1001.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Statistics from the Famous 1995 Standish Group Report.
Failures, Successes And Identifying Best Practices For Higher Success of IT Projects CHINOYEREM DEBORAH OKOROAFOR CHIMA W. ORIJI
Practical Investment Assurance Framework PIAF Copyright © 2009 Group Joy Pty. Ltd. All rights reserved. Recommended for C- Level Executives.
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
Software from Requirements Brent Haines April 12, 2007 Why Methodology Doesn’t Really Matter.
Software Design: Principles, Process, and Concepts Getting Started with Design.
L To identify the services that the customer requires from a system and the constraints under which it operates and is developed.
Chapter 13: Software Quality Project Management Afnan Albahli.
Academic Writing The Mechanics. Sentences  Must have a subject and a verb  and maybe an object  Who, what the subject is doing, to what  Pay attention.
T Software Development Project I Customer Info Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Chapter 1 The Requirements Problem
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
CSE SW Measurement and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M15 version 5.09Slide 1 SMU CSE.
Stages of design  High level design  High level data structure  Architecture  Low level design-code design  Algorithms  Low level data structures.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Project success = business success TM Introduction to Agility Agility is a comprehensive response to the business challenges of profiting from rapidly.
Software Engineering Saeed Akhtar The University of Lahore Lecture 3 Originally shared for: mashhoood.webs.com.
Homework #1a Lifecycle Paper For each stage of the life cycle provide a list of items you think should be there. There should be at a minimum of five items.
Describing MCM Mission Package Software Interoperability with Architectural Descriptions.
Overview of Addressing Risk with COSYSMO Garry Roedler & John Gaffney Lockheed Martin March 17, 2008.
Software Process Improvement ความรู้เบื้องต้นทั่วๆไป เกี่ยวกับ SPI.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Systems Architectures System Integration & Architecture.
Introduction to Software Requirement Engineering Nisa’ul Hafidhoh Teknik Informatika
Requirements Introduction Emerson Murphy-Hill. Scope of Software Project Failures WHY PROJECTS FAIL % 1. Incomplete Requirements Lack of user involvement12.4.
SQA project process standards IEEE software engineering standards
SQA project process standards IEEE software engineering standards
Manajemen Proyek Sistem Informasi
Component Based Software Engineering
Software Measurement Process ISO/IEC
CSE 403, Software Engineering Lecture 2
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Systems Architecture and Engineering
Presentation transcript:

Copyright ⓒ 2005 SE Technology. Co.,Ltd. All rights reserved. What are the differences between the architectural description of large scale software development and that of system development. SE Technology Ltd., IAE, 633-2, Koan-Ri, Packam-Myon, Yongin-City, Kyonggi-Do, , Korea IWFST2005, International Workshop on Future Software Technology 2005 Project Management Ph.D. Joongyoon Lee

Copyright ⓒ 2005 SE Technology, Ltd. All rights reserved. [ 2 ] Factors of IT application dev. projects failure Canceled Before Completion Cost Overrun (189 %) Time Overrun (222 %) 81 bill. $ loss / year (1% of US GNP) 59 bill. $ overrun / year US spend 250 bill. $/yr on approximately 175,000 IT appl. dev. projects. Meet Plan T23E-T10E STANDISH GROUP REPORT Recite : US % 16.2 % 31.1 % Project Impaired Factors 1.Incomplete Requirements 13.1 % 2.Lack of User Involvement 12.4 % 3.Lack of Resources10.6 % 4.Unrealistic Expectations 9.9 % 5.Lack of Executive Support 9.3 % 6.Changing Reqs. & Specs.8.7 % 7.Lack of Planning8.1 % 8.Didn’t Need It Any Longer 7.5 % 9.Lack of IT Management 6.2 % 10.Technology Illiteracy4.3 % 11.Other9.9 % Requirements Management Technical Other 28 % 52 % 10.5 % 10 %

Copyright ⓒ 2005 SE Technology, Ltd. All rights reserved. [ 3 ] The differences of Project Management between System and SW development System and software development projects are different from the view point of development target type, one is system the other is software. The detail contents of these Project Management process areas do not differ from system development project and software development project. Differences are the data which the project management activities deal with. The data, which contain architectural descriptions, are produced during Engineering and Support process. Basic Project Management PAs of CMMI

Copyright ⓒ 2005 SE Technology, Ltd. All rights reserved. [ 4 ] The Standard Process of ISO/IEC is Effective? PM Sys. Eng. When a system element is developed, an appropriate standard is applied corresponding to the nature of the system element. For system elements that are implemented in software, the processes of ISO/IEC are applied. Project Process Technical Process

Copyright ⓒ 2005 SE Technology, Ltd. All rights reserved. [ 5 ] SW Development Stages within System Life Cycle Stages of ISO/IEC ISO/IEC guides that after Architectural Design Process of system is performed, the processes of SW (ISO/IEC 12207) are applied for implementation. The guidance should be interpreted as that the Architectural Design Process should be completed before Software Development Process start. This means that the Software Development Process needs architectural descriptions of systems. As a matter of fact, lots of software development projects do not have enough architectural descriptions of systems at the start point. From this point of view, if there are not enough architectural descriptions of systems at the start point software development project, the project manager should perform the Architectural Design Process from the top layer of systems.  This is the activity to define right requirement of the SW component.

Copyright ⓒ 2005 SE Technology, Ltd. All rights reserved. [ 6 ] Results and discussion Key finding of the STANDISH GROUP ’s survey is that a high percentage of executive managers believe that there are more project failures now than five years ago and ten years ago. This despite the fact that technology has had time to mature. The cause of project failure depends more on the complexity of software. The cause of project failure depends more on the requirement definition. At the start point of the software development project, generally there are insufficient architectural descriptions. In this environment, the large scale software development project should be considered as system development rather than software itself especially at the software architecting stage. If there are insufficient architectural descriptions are vague requirement of the SW item at the time of contract or early stage of SW development project, the developer shall develop a top-level system design for the interfaces external to the SW item and between the SW component of the SW item.