Open AccessRational United Process Part - II Best Practices for Software Development Team
Author(s) -
Manoj Tharian
Publication year - 2003
Publication title -
mapana journal of sciences
Language(s) - English
Resource type - Journals
ISSN - 0975-3303
DOI - 10.12723/mjs.2.7
Subject(s) - business process modeling , artifact centric business process model , computer science , business process , process management , business rule , business process model and notation , business object , business process discovery , business process management , business requirements , business analysis , process (computing) , software engineering , engineering management , business model , business , engineering , work in process , operations management , marketing , programming language
One Of the major problems with most business engineering efforts, is frat the software engineering and the business engineering community do not communicate properly With each other. This leads to that the Output from business engineering is not used properly as input to the software development effort, and viceversc. The Rational Unified Process addresses this by providing a common language and process for both communities, cs we" os showing how to create and maintain direct traceability between and soft-wore rnodels. In Business Modeling we document business processes using so called business use cases. This assures a common understanding among a" stakeholders Of What business process needs to be supported in the organization. The business use cases cre analyzed to understand how the business should support the I O business processes. This is documented in a business object-model. Many projects may choose not do modéing. Requirements The goal Of the Requirements workaow is 'o describe What the system should do and allows the agree on that description. TO achieve