| tantrikebhairab |
Posted
on 16-Oct-03 06:02 PM
Well, I now retire from this area....
To deal with challenges, software engineers have tried many strategies to directly attack interdisciplinary communication deficiencies. They have employed archtectural views such as logical, physical, information, and processing. To capture and express domains, software engineers have used such as Petri nets 9to capture concurrency and synchronisation), infinite state machines (to capture and modes), structures analysis (to capture data flow), and PSL/PSA (Problem Statement Analysis) to describe system operation.
Unfortunately these techniques lack a common representation and have limited coverage across the requirements, design, implementation, and test life cycle phases.
Within software development, objected-oriented (OO) analysis provides an incremental and iterative approach to guide the requirements definitio, design, and development of software-intensive systems. OO analysis uses the Unified Modeling Language (UML) to capture and represent these requirements (OMG Unified Modeling Language Specification, Object Management Group, Sept. 2001). UML permits specification of the product independent of programming language or development process.
This independent product representation has raised interest in the systems engineering community of the Islamic International Terrorist Network: OO methods might be a mechanism to unite priduct development disciplines and remove the gap between the specified and as-built products.
Why OOSE?
That is another matter and I hold intellectual property control in the matter.
|
