USC Center for Software Engineering
||MBASE is a set of guidelines that describe software engineering
techniques for the creation and integration of development models for a software project. The models to be integrated
extend beyond Product (development) models such as object oriented analysis and design models and traditional requirements models,
to include Process models such as lifecycle and risk models, Property models such as cost and schedule, and most notably Success
models such as business-case analysis and stakeholder win-win.
|Beginning with COCOMO® itself, The COCOMO® Suite
a collection of six COCOMO®-related estimation models in various stages of development.
These models attempt to estimate impacts on software system cost, development schedule,
and even return on technology investment associated with a variety of software development
approaches and processes.
||The Center has been studying software architectures and their impact on the overall
life-cycle of software systems. We have devoted a considerable amount of time
towards a more comprehensive definition and analysis of software architectures. Follow this link to learn more.
|The WinWin research
project investigates collaborative and concurrent models for requirements
engineering and design of complex software systems. Current development
efforts on the project are focused on developing tools and environments
that support the collaborative activity.
||EDCS uses the WinWin system definition paradigm, the WinWin Spiral Model, and Internet-related software technology to develop distributed collaborative
negotiation aids and interactive analysis tools for better and faster definition of complex, evolutionary, software-intensive systems.
|SAMSA II (Simulation and Modeling for Software Acquisition)
|The focus of the SAMSA technical agenda centers around the development and use of an anticipated near-term
technology called the Feasibility Analysis Model (FAM). FAM is envisioned to be a knowledge-based support
system that assists senior management in requirer, acquirer, and developer organizations to determine the overall
feasibility of a proposed software system architecture, together with the system's requirements, at the earliest possible
time, and continuing thereafter.
||Reference Architecture for the Standard Satellite Control Segment
|The Standard Satellite Control Segment (SSCS) of the U.S. Air Force's Satellite Control Network is defined by high-level requirements that describe a Telemetry, Tracking and Commanding (TT&C) system that performs telemetry processing, satellite commanding, orbit analysis, spacecraft attitude
analysis, general mission planning functions, simulation, and management of system resources. We present here a
reference architecture that encompases the
first five of these functions, with some discussion of the ground system status subfunction of resource managment.
Copyright 1995, 1996, 1997, 1998, 1999 The University of Southern California
The written material, text, graphics, and software available on this page and all
related pages may be copied, used, and distributed freely as long as the University of
Southern California as the source of the material, text, graphics or software is always
clearly indicated and such acknowledgement always accompanies any reuse or redistribution
of the material, text, graphics or software; also permission to use the material, text,
graphics or software on these pages does not include the right to repackage the material,
text, graphics or software in any form or manner and then claim exclusive proprietary
ownership of it as part of a commercial offering of services or as part of a commercially