The hybrid process that combines traditional requirements and use cases

Systems Engineering

Volumn 7, Issue 4, 2004, Pages 303-319

  Daniels, Jesse ^a   Bahill, Terry ^a,b  

^a BAE SYSTEMS   (United States)

^b University of Arizona   (United States)

Author keywords

Engineering communication; Object oriented design; Object oriented systems engineering; Requirements; UML; Unified modeling language

Indexed keywords

ENGINEERING COMMUNICATION; OBJECT-ORIENTED SYSTEM ENGINEERING; UML;

OBJECT ORIENTED PROGRAMMING; SOFTWARE ENGINEERING;

SYSTEMS ENGINEERING;

EID: 24744451366     PISSN: 10981241     EISSN: 15206858     Source Type: Journal    
DOI: 10.1002/sys.20013     Document Type: Article

References (24)

1. S. Adolph and P. Bramble, Patterns for effective use cases, Addison-Wesley, Reading, MA, 2003.
2. F. Armour and G. Miller, Advanced use case modeling, Addison-Wesley, Reading, MA, 2001.
3. A.T. Bahill and J. Daniels, Using object-oriented and UML tools for hardware design: A case study, Syst Eng 6(1) (2003), 28-48.
4. A.T. Bahill and F.F. Dean, "Discovering system requirements," Handbook of systems engineering and management, A.P. Sage and W.B. Rouse (Editors), Wiley, New York, 1999, pp. 175-220.
5. G. Booch, I. Jacobson, and J. Rumbaugh, The Unified Modeling Language user guide, Addison-Wesley, Reading, MA, 1999.
6. M. Cantor, Rational Unified Process for Systems Engineering Part 1: Introducing RUP SE Version 2.0, http://www.therationaledge.com/content/aug_03/f_rupse_mc.jsp, August 2003.
7. M. Cantor, Rational Unified Process for Systems Engineering Part II: System architecture, http://www.therationaledge.com/content/sep_03/m_systemarch_mc.jsp, September 2003.
8. A. Cockburn, Writing effective use cases, Addison-Wesley, Reading, MA, 2001.
9. R. Davis and B.G. Buchanan, "Meta-level knowledge," Rule-based expert systems, the MYCIN experiments of the Stanford Heuristic Programming Project, B.G. Buchanan and E.H. Shortliffe (Editors), Addison-Wesley, Reading, MA, 1984, pp. 507-530.
10. S. Friedenthal, H. Lykins, and A. Meilich, Adapting UML for an Object Oriented Systems Engineering Method (OOSEM), http://www.omg.org/cgi-bin/doc?syseng/ 2001-09-05, 2000.
11. H. Gomaa, Designing concurrent, distributed, and real-time applications with UML, Addison-Wesley, Reading, MA, 2000.
12. R. Grady, Practical software metrics for project management and process improvement, Prentice-Hall, Englewood Cliffs, NJ, 1992.
13. IBM RUP, IBM Rational Unified Process, http://www-306.ibm.com/software/awdtools/rup/, 2003.
14. IBM RUP SE, IBM Rational Unified Process for Systems Engineering, available on the Rational Developer Network, www.rational.net (account required), 2003.
15. I. Jacobson, Systems of interconnected systems, Road to the Unified Process, Cambridge University Press, Cambridge, 2000a.
16. I. Jacobson, Use cases in large-scale systems, Road to the Unified Process, Cambridge, University Press, Cambridge, 2000b.
17. I. Jacobson, M. Griss, and P. Jonsson, Software reuse: Architecture, process and organization for business success, Addison-Wesley, Reading, MA, 1997.
18. I. Jacobson, M. Ericsson, and A. Jacobson, The object advantage: business process reengineering with object technology, Addison-Wesley, Reading, MA, 1995.
19. I. Jacobson, G. Booch, and J. Rumbaugh, The unified software development process, Addison-Wesley, Reading, MA, 1999.
20. D. Kulak and E. Guiney, Use cases: Requirements in context, Addison-Wesley, Reading, MA, 2000.
21. D. Leffingwell and D. Widrig, Managing software requirements, Addison-Wesley, Reading, MA, 2000.
22. Object Management Group: Unified modeling language: superstructure version 2.0 final adopted specification, http://www.omg.org/cgi-bin/apps/doc?ptc/03-08-02.pdf, 2003.
23. Ronin International, Enterprise Unified Process (EUP), http://www.enterpriseunifiedprocess.info/, 2003.
24. R. Young, Criteria of a good requirement, http.//www.ralphyoung.net/artifacts/CriteriaGoodRequirement.pdf, 2004.