Aplying UML and Paterns

Part1 Introduction: [Chapter 1] This chapter describe the different of the analysis
And design: The analysis is emphasize the investigation of the problem and
Requirement, rather than a sloutions. design is to fulfills the requirement rather
Than its implementation. Define the OOA/D is to finding and describe the objects in
The problem domain. and define the UML's concept in OOA/d, and what the UML cocould
Brings us in OOA/D. [Chapter2]: Define strate that the iterative development
(Iteration) and up's fundamental concepts. The iteration & up, is know as
Iterative and incremental development, it develop the system with little changes and
Not in a time, it always needs lots times steps by steps to achieve the requirement,
So changes is need in UP,. To make changes fit the requirement, we need do frequent
Feedback and adaptation in each end of the iterat, so the Iteration Development of up
Also called adaptive process, in contrast to the waterflow design, which is
Predictive process and so the key idea of iteration is shortly timeboxed, it shoshould
Not be too long compared with waterfolw desing, so it can brings the benefits
Correct the Desgin to fulfil the requirement in the early progress, rather than
Late migifation of high risk. The uniied process has four phase (inception,
Laboration, construction, transition), the phase also has totally different meanings
In contrast to the waterflows designs, the waterflows desing's phase or stage always
Not willing to feedback, or trying to fix the whole design in detailes at that stage
And then to the next one. But up design phase almost Cove all of the UP disciplines
(The workflows), so the iteration cocould feedback each disciplines for the future
Usage or next iterations, it do not trying to solve all of the detailes design at
Time. [Chapter3] Case Study, here, author try to describe the problem domain's issue,
It is emphasizes that to decide the responsibility to each layer is more important,
We shoshould find out the primary focus of case for demain object.
Part2 [inception] [Chapter 4] Skip, [Chapter5] understanding the requirement, introduce
The requirement's definition and furthermore, the key concept of up's requirment
Operations, and typs of requirements, and in common usage, requirements are categorized
As functional or non-functional.The functial requirement are supported Ed and recorded
In the use-case model, and others can be recorded in the use case they related
To, or, in the supplementary specifications artifact. And to sort the specified tural
Analysis, the quality requirements wowould likewise fundamentally strong influence also
To the ubuntual analysis.
[Chpter6] use-case model: Writing Requirement in Context: Introduction: The Essence
Is discovering and recording functional requirements. And about the use case itself,
Worthwhile, a story which depend on need is more better. Do REQUIREMENTS Work with
Focus on how a system can add value and fulfil goals. Use Case are
Requirement. black-box use cases are the most common and recommended kind, which
Focus on the responsibilities of a elements, specify what but not how the system
Must do. The format of use case is not important, the key things is to write
Details of the success scenario and Its Extensions.
Then author explaining the sections of the fully dressed example, each section has
His own responsibilites. And the author take out the goals and scope of a use
Case, which shocould depend on the levels (the too low level is a common use case
Misktake) Base One the EBP guiderline (only used to dind out of the dominant level
Use), could t that, it is can be separate and can aviod the duplication of the text. It
Is interesting that the author give us a good define of the use goals and use case,
The use goals always cocould be moved higher up the goal hierary (what is the goal
That goal), reverse, the use case-oriented question cocould be what do you do.
Filter out the excessive low level use case is the EBP guidline's job.
OK, we already got the basic ideas of the use case, then it times that we study
Finding out the primary actors, goals, and use case. To find the right primary actors
From the messy reality we shoud clear the different between the primary and
Supporting actors, knew the relationship between the actors and goals, and the key
Point is the Goals shocould obey the EBP process (in Chinese saying: time and location characters), and
To check the Goals is or not applying the EBP, we can try to think its High Level
Goals, then can judge it is or not.
[Chapter7] roughly Skip, [chapter8] from inception to elaboration. I m just feeling
Good that now seems to have move to a high level of UML, the elaboration, this Chater
Indicate the elaboration step. Compared with the inception (a short step to determine
Basic feasibility, resk, and scope, and decide if the project is worth more serious
Investigtion), The ealaboration, in one sentence, build the core architecture, resolve
The high-risk elements, define most requirements, and estimate the overall schedule
And resources. And in ubuntually significant in elaboration, it has, employing
"Wide and shallow" design,. 1 indentifying the separate processes, layers, pachages, and
Subsystems, and their high-level responsibilities and interfaces.2 refining
Inter-module local and remote interfaces, include the finest details of the Parameters
And return values. A stable interfaces is hopes out.3 integrating existing
Components.4.implementing simplified end to end scenarios. key ideas manifest in
Elaboration include:. 1 do short timeboxed risk-Drivern iterations. 2 start
Programming early.3 adaptively design, implement, and so on,. 3 tes early.5adapt based
On feedback. 5 write most of the Use caase and other requirements in detail, through
Series of workshops. And in this phase it will emphasizes a range of fundamental and
Common OOA/d skills used in building object systems, such as assigning
Responsibilities to objects.
Part3 elaboration: iteration 1: [Charpter 9] Now we are entering the first real
Development iteration. Before desing the system it is necessary for us to do
Investigation of the problem domain, and the clarification of the Input and Output
System event is a start. In UML, we will use the SSD in use-case model to began our
Analysis. The SSD is used for describe the system behavior which is a discription
What a system does in black box, and include the SSD, use case and system contracts.
Draw the SSD, We shocould clearfy the event and event's operations, care the define
The system boundary and the SSD is from the use case, to name the SSD event and
Operation by intent meanings. and as part of the use case, SSD is chosen for
Scenarios which is really needed.
[Chappter 10] domain model (Conceptual Model): Visualizing concepts: the use case are
An important requirement analysis artifact, but not object-oriented, but the domain
Model is the most important aritfact to create during OOA.