Bibliography: p. 94-95. / Contract no. DA36-030-AMC-03200(E).

Martin B. Brilliant. / "March 3, 1958." Based on a thesis submitted to M.I.T. Dept. of Electrical Engineering, January 13, 1958. / Bibliography: p. 58. / Army Signal Corps Contract DA36-039-sc-78101. Dept. of the Army Task 3-99-06-108 and Project 3-99-00-100.

by Michael Athans and Sanjoy K. Mitter. / Final report / Bibliography: p. 17-19. / "March 1979." / Grant AFOSR-77-3281B

S.S. Sastry, C. Desoer and P. Varaiya. / Bibliography: leaf 4. / Caption title. "August, 1981." / Supported by DOE under Grant ET-A01-2295T050 NSF Grant ENG-78-09032-A01

S.S. Sastry, C. Desoer and P. Varaiya. / Bibliography: leaf 4. / Caption title. "August, 1981." / Supported by DOE under Grant ET-A01-2295T050 NSF Grant ENG-78-09032-A01

Omar Hijab, Shankar Sastry. / Bibliography: leaf [4]. / Caption title. "September, 1981." / Supported in part by NASA Grant no. 2384 Office of Naval Research under the JSEP Contract N00014-75-C-0648 DOE Grant no. ET-A01-2295T050

University of Macau / Faculty of Science and Technology / Department of Mathematics

Since the Software Engineering Institute published the Capability Maturity Method Integration (CMMI) in 2003, many software firms have implemented it to enhance its software quality assurance and international collaboration. Analysis and design phases are two important phases for the software development. The artifacts of these two phases mainly represented using the structured technique or the object-oriented technique. This study proposed a methodology which provides guidelines to compare the artifacts of these two techniques for an embedded system. The research methodology is articulated using the design science research methodology. A usability valuation with a real-world embedded system case is performed to demonstrate its applicability. The results provide evidences to enhance our understanding about the strength and weakness of these two nalysis and design techniques.

Object-Oriented analysis and design approach has become the mainstream of today¡¦s systems development technique. The Class Diagram in Unified Modeling Language (UML) is the major tool for modeling the class structure in the object-oriented system analysis and design process. Once the class diagram is constructed, class normalization needs to be performed to eliminate the anomalies for the designing a database. However, the detailed guideline for performing class normalization is lacking. Therefore, this study presents a class normalization methodology based on object normal forms proposed by Ambler (1996). Two real-world cases are presented to illustrate the concepts, application, and the advantages of using the proposed method. Using this methodology in class modeling will help system developers normalize the class design in advance, and thereby enhance the efficiency and effectiveness of system development.

Due to the fact that the environment which business confront is very dynamic, so the business require the software to reduce the response time, provide the high quality, and supply the flexible modeling process and high maintainability. In order to meet the requirement, a new software solution is emerged. Component-based software engineering is a method to integrate existed component to produce faster speed, lower cost and higher quality software. And it is concerned with the rapid assembly of systems from components where components and frameworks have certified properties; and these certified properties provide the basis for predicting the properties of systems built from components. Therefore, component based software engineering replace the position belong to traditional software engineering progressively, it become the next generation software engineering paradigm. Because businesses want to transform their requirement to be final components, so the component-based software engineering must have component modeling methodology in the system analysis stage. For this reason, the advantage and disadvantage of the component modeling methodology makes a very deep influence on component-based software engineering. And after the survey we made, we discover the greater parts of the existed component modeling methodology have a lot of defects, for example: the modeling method stay at abstract level, lack of clear and definite modeling rules, short of consistence of process document and can¡¦t meet the good component modeling characteristics. Fortunately, in our surveyed methodology, we discover the ¡§UML Component¡¨ is a component modeling methodology which can meet the good component modeling characteristics and have the develop potential. But the ¡§UML Component¡¨ methodology still has some problem, for example: lack of explicit component identify rules, complete tools support and simply modeling process. Due to these reasons, our study provides three solutions to refine and extend the ¡§UML Components¡¨ methodology. First of all, we utilize the use case identify method by [§d¤¯©M2002]¡Bthe concept of ¡§Fan-in and Fan-out¡¨ by [Marquis2002] and the use case association transform method to refine the problem of component modeling rules. Secondly, we employ data glossary, data relation matrix and operation reference matrix to improve the problem of component modeling tools. Finally, we redesign the process model which includes four stages as follows, requirement acquisition, component identification, component interaction and component specification to resolve the irrational parts of original modeling process. With this refined methodology, the system analysts can follow the stand modeling rules and process. In the other hand, the system developer also can develop the system which meet the business requirement exactly, ensure the component quality and speed up the software develop rate.