SE Technology Ltd., IAE, 633-2, Koan-Ri, Packam-Myon, Yongin-City, Kyonggi-Do, 449-863, Korea

1. IWFST2005, International Workshop on Future Software Technology 2005 Project Management What are the differences between the architectural description of large scale software development and that of system development. Ph.D. Joongyoon Lee leejy@se2u.com SE Technology Ltd., IAE, 633-2, Koan-Ri, Packam-Myon, Yongin-City, Kyonggi-Do, 449-863, Korea

2. Project Impaired Factors Incomplete Requirements 13.1 % Lack of User Involvement 12.4 % Lack of Resources 10.6 % Unrealistic Expectations 9.9 % Lack of Executive Support 9.3 % Changing Reqs. & Specs. 8.7 % Lack of Planning 8.1 % Didn’t Need It Any Longer 7.5 % Lack of IT Management 6.2 % Technology Illiteracy 4.3 % Other 9.9 % 16.2% 31.1% US 1995 52.7% Factors of IT application dev. projects failure Recite : http://www.cs.nmt.edu/~cs328/reading/Standish.pdf T23E-T10E STANDISH GROUP REPORT US spend 250 bill. $/yr on approximately 175,000 IT appl. dev. projects. 81 bill. $ loss/year (1% of US GNP) Meet Plan Canceled Before Completion 59 bill. $overrun /year Cost Overrun (189 %) Time Overrun (222 %) Other Requirements 10 % 52% 10.5 % Technical 28 % Management

3. The differences of Project Managementbetween 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. Basic Project Management PAs of CMMI • Differences are the data which the project management activities deal with. • The data, which contain architectural descriptions, are produced during Engineering and Support process.

4. The Standard Process of ISO/IEC 15288 is Effective? PM Project Process Sys. Eng. Technical Process • 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 12207 are applied.

5. SW Development Stages within System Life Cycle Stages of ISO/IEC 15288 • ISO/IEC 15288 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.

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.