Page 126 - DCAP308_OBJECT_ORIENTED_ANALYSIS_AND_DESIGN
P. 126

Object Oriented Analysis and Design




                    Notes          We must get in to the correct frame of mind to attack this phase correctly. We must try not to get
                                   bogged down with too much detail, especially implementation details.

                                       !

                                     Caution We need to have a very broad view of the system and understand system-wide
                                     issues.

                                   Prototyping

                                   A key activity in the Elaboration Phase is the mitigation of risks. The sooner risks are identified
                                   and shot down, the lesser their impact will be on the project. Prototyping difficult or problematic
                                   areas of the project are a tremendous help in the mitigation of risks. Given that we don’t want to
                                   get bogged down in implementation and design at this phase, the prototypes should be very
                                   focused, and explore just the area of concern. Prototypes can be thrown away at the end of the
                                   exercise, or they can be reused during the construction phase.
                                   Deliverables


                                   Apart from prototypes, we are going to develop two UML models to help us towards our goal
                                   of understanding the problem as a whole. The first model is the Use Case Model. This will help
                                   us to understand what the system needs to do, and what it should look like to the “outside
                                   world” (i.e. the users or perhaps the systems it must interface to).
                                   The second model is the Conceptual Model. This model allows us to capture, using UML, a
                                   graphical statement of the customer’s problem. It will describe all of the major “concepts” in the
                                   customer’s problem, and how they are related. To build this, we’ll use the UML Class Diagram.




                                     Notes We will use this Conceptual Model in the Construction Phase to build our software
                                     classes and objects.




                                      Task       Compare and contrast feasible time and required time.


                                   Self Assessment

                                   Fill in the blanks:
                                   1.  ..................... describe how system behaves from the user’s point of view.

                                   2.  ..................... is used to automate manual process.
                                   3.  ..................... is used to combine functionality from different system
                                   4.  ..................... is the point where you want to have a better understanding of the problem.

                                   5.  A key activity in the Elaboration Phase is the mitigation of .....................
                                   6.  ..................... difficult or problematic areas of the project are a tremendous help in the
                                       mitigation of risks.

                                   7.  ..................... Model allows us to capture, using UML, a graphical statement of the customer’s
                                       problem.



          120                               LOVELY PROFESSIONAL UNIVERSITY
   121   122   123   124   125   126   127   128   129   130   131