Just another WordPress weblog

Analyst: represent unified model design of requirement
not from his point of view but (as described in requirement).

1. Understand requirements.
2. Determined needed from requirements (Function).
3. Determined if needed is possible or not as logic.

    

• And begin in steps of dealing will complexity (abstract-decomposition-hierarchy).

Designer: deal with models to
determined details of models that needed
(if it declared or not).

To deal with Complexity
we have 2 ways (function Decomposition-Function oriented-, object oriented)

Function Decomposition: partitioning system to function to be understandable (use case).

Object oriented: deal with obj. and details of use case (Class diagram and dynamic behavior).

Software Lifecycle Questions

• Which activities should I select for the software project?
  
  • According to life cycle type.
    
    • What are the dependencies between activities?
      
    • How should I schedule the activities?
      
  • Estimate right time for project.
    
    • What is the result of an activity?
      
  • Result of activity is the only role that to determined which finished and not from life cycle.