Advertisement

An Empirical Development Case of a Software-Intensive System Based on the Rational Unified Process

  • Kilsup Lee
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3984)

Abstract

The Rational Unified Process (RUP) is a development process which is based on object-oriented, usecase-centric, architecture-centric, and iterative approaches. Most projects for public organizations have adopted waterfall model in software development lifecycle, however, various projects have recently tried to apply an iterative model to minimize risks and to enhance quality of software. But empirical results of software-intensive development based on the RUP are not well known. Therefore, this paper presents process, period, effort and quality factors for a software-intensive system development through the study on the Korean Core Instrumentation System (K-CIS) which has adopted the RUP. We also present the result of comparison between the K-CIS RUP and waterfall model, and lessons learned from the K-CIS case. We believe that our result is useful for establishment of a process and estimation of resource and quality factors for software-intensive systems efficiently.

Keywords

Business Modeling Software Development Process Embed Software Iterative Model Software Requirement Specification 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Dennis, A., Wixom, B.H., Tegarden, D.: Systems Analysis and Design with UML 2.0 - An Object-Oriented Approach, 2nd edn. Wiley, Chichester (2005)Google Scholar
  2. 2.
    Braude, E.: Software Engineering - An Object- Oriented Perspective. Wiley, Chichester (2001)Google Scholar
  3. 3.
    Sterling Software, Inc.: Sterling Software Component-Based Development Method. (available with COOL:Spex and COOL:Gen products), http://www.sterling.com (2005)
  4. 4.
    Cheesman, J., Daniels, J.: UML Components - A Simple Process for Specifying Component-Based Software. Addison-Wesley, New York (2001)Google Scholar
  5. 5.
    AEW Services: The Role of the Project Life Cycle (Life Span) in Project Management. AEW Services, Vancouver, BC (2003)Google Scholar
  6. 6.
    Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley, Reading (1999)Google Scholar
  7. 7.
    Philippe, K.: The Rational Unified Process - An Introduction, 2nd edn. Addison Wesley, Reading (2000)Google Scholar
  8. 8.
    MND: Directive on National Acquisition Management Process - Automated Information System. Directive, No. 727, Ministry of National Defense (2003)Google Scholar
  9. 9.
    C4ISR AWG: C4ISR Architecture Framework. Ver. 2.0 (1997)Google Scholar
  10. 10.
    DoD: DoD Architecture Framework. Ver. 1.0 (2003) Google Scholar
  11. 11.
    TRADOC: Operational Concept Description of Core Instrumentation System. Korea Advanced Combat Training Center (1999)Google Scholar
  12. 12.
    DoD: Software Development and Documentation. MIL-STD-498 (1994)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Kilsup Lee
    • 1
  1. 1.Dept. of Computer & InformationKorea National Defense UniversitySeoulRepublic of Korea

Personalised recommendations