This week,I have learned chapter 7-14 of this book,this is the second time learning it.
There are four typies of diagram in OO analysis.They are class diagram,use-case diagram,interaction diagram(sequence diagram or collaboration diagram),state diagram.
I have a question is if struts class should be imported in at this phase.I learned a book there is a seqence diagram,it includes struts class.But,I think,we should know what should we do in the analysis phase.the result should be used in any oop design,for example:.net.So,I think struts class shouldn't be imported at this time,but design phase.
The state diagram is used to create method in a class.But I don't know it clearly.
After analysis phase,We should choose a plan according with the environment and post it to the manage department.
In design phase,the package diagram is used to dividing sub system.at this phase,We should use state diagram to write pseudocode of a method's logic of a class.
The most valuable knowledge come from chapter 10--datebase design for me.especially oodb.The ability of OODB is exciting for me.It can support self definition data type and inheritance and other new charactor that relation db can't support.I should learn it later.
In our LD project,We should use another db type it between relation db and oo db called hybrid object-relational DBMS.
In hybrid object-relational DBMS,if there are several child class for a parent class. the child class can be processed in two ways.one is using a table that represent a super set of all these class,another is every child class is a table and the key of this table is outer-key(I can't understand it).
The main content of Chapter 11,12 if I/O,control design,chapter 12 emphasis Human-Computer Interface design base on chapter 11.It present a thinking is "all is for user".HCI in OOP design can be produced from sequence diagrams.
The part four of this book tell us knowledge about executing and support,there is chapter 13-15 in this part.
Chapter 13 tell us RAD and component-based development.RAD cover the knowledge include tool,technique and developing model.
The risk management of project should put in our mind when developing a project,especially take spirial development approach,like our LDP.In this chapter,I knew the struts is a object framework,like J2SE,J2EE,Hibernate,etc....I knew a object framework should be decided before detail designing also.
Chapter 14 tell us software package and ERP.Software package schema is the tendency now.The future of ERP will include supply-chain management and business intelligence.I knew an ERP system called SAP in this chapter.
I have read chapter 2-5 in e-book named <<javauml>> roughly.
From these chapter,I knew some knowledge below:
1.the development flow in Unified Process is a spirial development approch;
2.the working flow in an iteration of project is:collect requirement->event list->use-cases diagram->class diagram...
3.there is a type of use-case named shdow use-cases,it includes:Security,Audit,Parameter,Maintenance,Archiving,Architecture Infrastructure.
4.the jsp page is a boundary class that we could indirectly say it will be java classes implementing the servlet inerface.
next week,I will finish the last chapter of <<system analysis and design>>,and read the remainder content of <<javauml>> roughly.
We will learn system analysis and design when processing our new learning platform project.