分类：设计

  Today,I have learned chapter 11 of this book-I/O and control design.

I think the control design with our LD project,there are three tyies of user in our program,they are admin,register user,non-register user,and we should add another type of user is block-manage user.There isn't affair recording function in the current version of LD program,we should add it in our future program.

  The original resource of the input and output design is DFD or sequence diagram.

  The message that send by actors to the object in the system is the resource of input design.and versus,is the output design.

chapter 12 human-computer interaction

  this chapter is the extend of I/O in the chapter 12,and it throughs emphasis on the human self.From the standard point of user,the interface of application system is system itself.

  In this phase,the interface class has been imported,and it should be embed in the classes of question domain in the sequence diagram and other diagrams.

  I think,the jsp pages should be imported in the sequence diagram or other diagrams.

execute and support

chapter 13 RAD and developement base on component

  1.spiral development approach:the initial plan should include the global plan of whole project.

  2.I think,the jfc and j2se,j2ee and struts,hibernate are all the classes of object-framework,so the struts class should be imported at design phase.for example,the sequence diagram.

  3.There are only two typies of component framework,they are Common Object Request Broker Architecture(CORBA) and Distributed Component Object Model(DCOM) said in this book.But,is the EJB or JavaBean component framework?

chapter 14 execute and support

 from this chapter,I knew the key of success ERP is the people in the company.

  The future of ERP is the deep and wide integrity.the increase point are the supply-chain management and business intelligence.

  I think,there is BPR,should there be LPR(Learning Process Reengeering) too;there is ERP,should there be LRP(Learning Resource Plan) too.but,where is the LPR or LRP?They are in our learndiary.com!

1.unified process:

1)at a minimum,all process will produce class,sequence,and use-case diagram;

2)chapter 2:

this chapter examines how uml,coupled with a sound software process model,such as the unified process,can produce...ever-changing...

3)chapter 3:establishing the project vision:

 inception phase:

(1)actors:

 actors are usually thought of as human beings,but they may be also other system,timer and clocker,or hardware devices.actors stimulate the system and are the initiators of events;they also can recieve stimuli from the system and in this case are considered passive.

(2)events list and events table:

external events and internal events

(3)business rules

4)chapter 4:use-cases

(1)getting to use-cases

features->event list->event table->use-cases

(2)happy.alternative.expective pathway(I don't know them.)

(3)shadow use-cases:

the use-cases that not a "functional  requirement".

they includes:security,parameter maintenance,audit,archiving,architecture infrastructure

This is a question:Are there use-cases involving the struts framwork?

(4)the increment plan for the project

this is the end of inception  phase,the result is requirement model.

22:06 05-1-5 p111

16:03 05-1-10

chapter 5 class

1.This is the begin of the elaboration phase.

2.this chapter tell us how to build a class diagram,includes identifing the class,three typies of class:entity,boundary,control class,relationship of classes.

3.I have seen the jsp is a special boundary class that extends from servlet.

the fruit at the end of this chapter is the analysis model.

I found a difference between the traditional model and the Unifield Process:  traditional model:analysis phase:event table,use-cases,class diagram,interaction diagram,state diagram;design phase:design class diagram,database,interface.

Unifield Process:first inception phase:events table,use-cases,increment plan;

elaboration phase:class diagram,dynamic diagram(interaction,state...),database,interface...

Maybe,I havn't uderstood the Unifield Process really.

chapter 6 building prototype

1.this chapter is in the elaboration phase.

2.tell us:

  1)how to build a user interface prototype?

  2)screen structure chart

  3)get feedback from user which studing the user interface prototype.

chapter 7 dynamic diagram

1.in the elaboration phase

2.tell us:

  how to build all kinds of dynamic diagram:interaction diagram(sequence diagram,collaboration diagram),state diagram,activity diagram,and some non-UML in the design named usage matrices.

3.A sentence in the end of chapter 8 that is:After the requirements have been solidified and the design work has begun, three architectures must be considered.from this sentence,I knew the fruit in the chapter 7 is the result of traditional analysis phase.

chapter 8 exection architecture design

1.in the elaboration phase

2.the java,jsp,j2ee,javabean,EJB,all of these concrete technique are presented in this chapter,the result of this chapter is exection architecture  of the project.

3.the system structure:

there are six logical tier:

Presentation Services,Business Context Services,Business Rule Services,Data Translation Services,Data Access Services,Database Services

21:40 05-1-10

p253

12:18 05-1-11

p280

the address of this book:www.jacksonreed.com OR www.awl.com

13:39 05-1-11

p293

the summary of chapter 9-12

chapter 9 data persistence: store object

1.in the elaboration phase

2.map the relationship to the ralation database:

simple Association,inheritance,generalization/specialization,aggregation and composition,reflexive

3.

  This week,I have learned chapter 7-10 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).

  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.

  This week,I have learned chapter 7-10 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).

在看<<系统分析与设计>>这本书的同时，我开始看javauml这本英语版的电子书，上周看了１０多页，由于英语水平有限，懂了个大概意思。这本书的起点较低，就是不懂uml和oop的人也可使用，只要有点java基础。作者先前写vbuml。

    这本书的重点是uml，用于jsp+tomcat的非商业应用，没有讲struts。（ucommercially available through Rational Software called the Unified Process and one from my own experiences called Synergy. The greatest emphasis will be placed on the Unified Process.）

    先讲了不应用uml的困境，然后讲了迭代和增量的区别。懂了个大概。

    我看这本书的目的是配合＜＜系统分析与设计＞＞的学习，用于把uml用于jsp程序的建模的实践。

    上周，看了这本书的第２－５章。

    心得如下：

    １、在项目管理中，与成员的充分、深入交流是至关重要的。可我现在连上网的时间都不能保证，看来，与大家的日常交流只有委托其他人了；

    ２、在基于迭代的开发方法中，蛛网模型（也是螺旋模型）是比原型法（增量模型）更彻底的迭代。可以最大程度的抗拒需求不定的风险，但是更难管理。原来yinhe给我提过螺旋模型，我当时搬照＜＜软件工程＞＞的自考书的概念，认为螺旋模型不适用于面向对象的开发方法，现在看来，我对螺旋模型的理解有问题了。我将继续探讨这个问题；

    ３、在需求分析阶段，有多种方法可以用来定义问题。对比我们的开发小组，我觉得可以采取调查表、qq访问等方式来进行，所以，我在章程中添加了开发小组成员如果两周内不回复调查表视为自动退出，不知道这有益还是有害于开发小组工作的开展；

    ４、在需求分析阶段，主要目的是明白问题域，回答让系统“做什么”的问题，因此不会涉及到具体的技术，也就是，需求分析的成果不仅可以用于jsp，也可以用于.net。

    我现在认为，在struts中的类应该在设计阶段引入，作为实施类。我觉得，在rose等工具中，应该可以自动引入某个类库。

    设计阶段与分析阶段的差异主要是类图的具体化，并且引入一些实施类，如界面等，并设计数据库。。。，但我现在现在还不知道jsp页面在设计中怎么处理，有一个英语电子书＜＜javauml＞＞我在下周可以看一下。我把旧电脑搬到乡下去了，不过不能上网。

    希望有朋友看了我的日记可以指出其中的错误，我在这里感激不尽。

    在把这本书大概的游览后，我准备结合我们的学习日记开放源码项目的需求分析来详细的学习一下这本书。

今天学习第一章：现代系统分析员涉及的领域，主要有如下心得：

    １、系统分析大部分工作不是程序设计，书中的系统分析员说她工作时的大部分时间是采访、报告、写信...

    ２、商业的信息系统类型：事务处理系统（TPS）、管理信息系统（MIS）、主管信息系统（EIS) 、决策支持系统（DSS）、通信支持系统、办公支持系统

    ３、系统分析员除了技术知识与技能，还需要商业、人际方面的，还需要诚实与道德

    ４、系统分析员会面临从桌面系统到internet的各种信息系统的配置。

    ５、系统分析员除了完成解决具体商业问题的信息系统，还有可能卷入企业的战略经营问题，如开发主管信息系统、业务流程再造（ＢＰＲ）、ＥＲＰ。

    ６、信息系统战略计划的结果：提交技术结构计划、应用程序结构计划和实施的时间帧。

    ７、系统分析员的工作会贯穿软件生命周期的整个阶段。

我们开发的学习日记是属于辅助教育平台，不在上面所说的商业系统之中，但是分析方法应该是通用的。

    对应商业系统所需的商业技能，这个系统的分析应该具有教育学习知识的技能，尤其是有关信息时代的自助式学习技能，这种技能是我现在严重缺乏的，可以通过两个途径补充：聘请这方面的专家作顾问、及时补充学习有关的知识。

    在学习日记的分析中，我们面临的分析任务是处在internet中的。

    我们在分析中，可以对应于商业系统的业务流程再造的概念，提出“自我教育流程再造”（STPR:self teching process reengineering）的概念，以新的信息时代的学习理论和学习实践，进行信息时代的自助式学习平台的建设。

    这个学习平台是一个通用的平台，应该为大家进行信息时代的自助式学习提供一揽子服务，为了建好这个平台，应该制定一个长期的战略计划。书中的落基山运动用品商店的战略计划用２００１－－２００４年这４年的时间来完成，我们这个平台的战略计划是什么？要用几年来完成呢？慢慢想吧。

       我今天买了一本＜＜系统分析与设计＞＞的书，６５元，John W.Satzinger Robert B.Jackson Stephen D.Burd著，朱群雄，汪晓男 等译。＜＜机械工业出版社＞＞＜＜中信出版社＞＞。我翻了好几天了，觉得还可以样。

    今天，参加了软件工程自学考试。自我感觉觉得会通过。但是，有如下几个问题需要再学习：

１、画数据流图，并将其转换为软件结构图。

    考的是一个用银行卡在自动取款机上操作流程。

    插入卡－＞检查卡（通过后）－＞接受密码（通过后）－＞接受钱款数量（未超支通过后）－＞在相应帐户上取款，更新帐户－＞显示清单－＞用户确认（通过后）－＞取款。

２、软件复杂性McCabe度量法：

    程序流程图转换为程序图，计算环路复杂性：V(G)=m-n+2p。

３、增量模型的增量方式分为增量提交、增量开发

４、软件结构优化准则（结构化分析各面向对象分析都适用）：

    １）划分模块时，尽量做到高内聚、低耦合；

    ２）一个模块的作用范围应在控制范围之内，且判定所在的模块应与受其影响的模块在层次上尽量靠近；

    ３）模块的深度、宽度、扇入、扇出要适当

    ４）模块的大小要适中；

    ５）模块的接口要简单、清晰、含义明确，便于理解，易于测试、实现和维护。

５、Jackson方法