Performance-oriented design model of the content & style of Software Engineering textbook for undergraduate computer software related majors

With the computer software and technology continuously improving, because of various factors influencing, computer engineers are very tough on how to improve the quality of software products, this is a bottleneck problem we must solve. We think that the information engineering combining with the philosophy thought would make engineer’s ideas suddenly enlightened. We find a method and model to solve software engineering problems from the philosophical Angle, and put forward the importance of information philosophy in the study of information engineering by standing at this altitude of the information engineering. As a new field, information philosophy provides a unified, convergence theory frame, it can satisfy the requirement of further specialized. Information philosophy will become most exciting and productive philosophy research field in our era's.

Download Full-text

Transforming an HCI Model to a Software Design Model

International Journal of Software Engineering and Knowledge Engineering ◽

10.1142/s0218194097000072 ◽

1997 ◽

Vol 07 (01) ◽

pp. 145-167

Author(s):

Andrew M. Olson

Keyword(s):

Software Engineering ◽

Human Factors ◽

Software Design ◽

Design Model ◽

Software Project ◽

Software Engineering Process ◽

Final Code ◽

Action Grammar ◽

Project Life

The software engineering and human factors communities are seeking ways to integrate their methodologies. This paper outlines an amplified, software engineering methodology that extends beyond requirements gathering to encompass human factors analyses. The methodology employs an object model that is uniform throughout the software project. It involves a procedure that seamlessly transforms a task action grammar model, from HCI theory, directly into a specification model based on user/machine dialog and, thence, into a software design model. The model's object-oriented structure makes it feasible to trace the effects of the user's needs throughout the amplified project life cycle to the final code. A case study documents evidence concerning how effectively the procedure supports the software engineering process. An examination of the extent of metamorphosis the model undergoes in the case study indicates that the transition through the amplified life history is well controlled; in particular, the transition from the software specification to the design model is more controlled than that under traditional methodologies.

Download Full-text