Μεθοδολογίες και Εργαλεία Ανάλυσης και Σχεδιασμού Π.Σ.
Embed Size (px)
Transcript of Μεθοδολογίες και Εργαλεία Ανάλυσης και Σχεδιασμού Π.Σ.
* .. 2011-2012 7
*Rational Unified Process (RUP) Rational Software Corp.
*/35 RUP; vs .
UML (Configurable process) (Best practices)
*/35 (iterative) components (UML)
*/351 : (phases) (inception phase) (elaboration phase) (construction phase) (transition phase)
*/35 (Initiation phase) 1/2Vision documentUse-case model (10%-20%) Business case Business model (prototypes)
*/35 (Initiation phase) 2/2
*/35 (Elaboration phase) 1/2 , ,
Use-case model ( 80%)- business case
*/35 (Elaboration phase) 1/2
(vision) ( ); ; ;
*/35 (Construction phase)
; ; ;
*/35 (Transition phase) 1/2beta testing
*/35 (Transition phase) 2/2 :
*/352 : (disciplines/ workflows)
*/359 (workflows) (business modeling) (requirements) (implementation) (test) (deployment) (configuration & change management) (, )
*/35 (process) A process describes who is doing what, how, and when
Workers (), (who)Artifacts (), (what)Activities (), (how)Workflows ( ), (when)
*/35 (Worker) . (Behavior) (Responsibilities) (artifact) (Team members can wear different hats.)
*/35 Activity: Find use cases and actorsStep: Find Actors Step: Find Use Cases Step: Describe How Actors & Use Cases Interact Step: Package Use-Cases and Actors Step: Present the Use-Case Model in Use-Case Diagrams Step: Develop a Survey of the Use-Case Model Step: Evaluate Your Results
*/35 (Artifact) : Use-Case (Design Model) (model element) (Design Class) Use Case (Source code) (executables) .. Requirements Specification, Software Development Plan
*/35 .. (Worker) (Activity) (Artifact)Describe a Use Caseresponsible forUse-Case Specifier , (source code, models, documents )
*/35 RUPUML use cases
*/35 Use-Case (Actors) Use-Case ( ) use case Preconditions post-conditions (optional)
*/35 Use-Case , (functional requirements)
use case RUP
. & 2 Use-Case ActorUse Case
use case actor.
. & ActorSystem (Actor) Actors ,
. & CharlieasdepotstaffCharlieasdepotmanagerCharlieDepotStaffDepotManager (Actors)
. & Use CaseUse Case actor actor .
. & Use Cases
*/35 Use Cases UML (verification)(realization)Use-Case Model(requirements)Implementation Model(source code) (Test Model)(test cases and procedures)(Influence)Design Model(classes and objects)
. & Use CasesAnalysis ClassesSourceCodeExecDesign Classes Use Cases
Rational Unified Process
****The steps of this activity can be divided into thinking, performing, and reviewing.*The steps of this activity can be divided into thinking, performing, and reviewing.*This shows how the RUP represents the process graphically. The UML provides a notation for representing the artifacts of the process, but not the process itself. These conventions will be used in describing each of the workflows of the process.*It is helpful to have some examples ready to use. You can add to the course registration example provided. For example, a precondition for the Register for Courses use case could be that the student has already enrolled in the university. *It is helpful to have some examples ready to use. You can add to the course registration example provided. For example, a precondition for the Register for Courses use case could be that the student has already enrolled in the university. ***Actor is a role, not a particular person or thing. The name of the actor should represent, as clearly as possible, the actors role. Make sure that there is little risk of confusing one actors name with another at a future stage of the work.
*Other example: To an ATM system, Charlie could act as a Customer, but also as an Operator (maintenance user) of the ATM. Important to get away from persons (especially in BE but important here also), as its easier to make changes to a role (or task) than to a persons job.
**The purpose of this diagram is to familiarize the student with the rich language of the UML which is available to represent software artifacts. You should NOT try to explain all the notation, just the purpose of the diagram and how to read it (superficially).A use case has a set of properties: brief description, flow of events, special requirements, etc. Use cases are enclosed in the use-case-model artifact.*As in traditional engineering disciplines (e.g., electrical and civil), models are the language of designer.
Note: The Rational Unified Process is use-case-driven. A use-case model is used to drive design, development and testing of the project throughout the project lifecycle. Come to an agreement with the customer on what the system should do (Use-Case Model)Assure that the design matches the requirements (Design Model)Produce source code that matches the design (Implementation Model)Verify and Validate the delivered product against the requirements (Test Model)
In this course, we will be concentrating on the Design Model (the Data Model is considered part of the Design Model, but will not be addressed in detail in this course).
The other models are each developed in separate RUP workflows.*Some of the work done in analysis is thrown away. This is not bad, since you need to play with the ideas to see what works and what doesnt, but you should expect that much of the work done during analysis is a kind of structured doodling. The biggest mistakes happened when people assign too much value to the early results of analysis. *