Object Oriented Software Engineering   View all facts   Glossary   Help

subject > representation > model > system model

system model
subject			fact

system model	contains the system domain model user interface classes classes representing aspects of the system's architecture such as clients, servers, files, and databases utility classes that make parts of the system more reusable, easier to maintain or easier to connect to other systems
	contains elements that do not represent things in the domain, but are needed to build a complete system
	contains elements that represent things in the domain
	is a subtopic of 5.8 - The Process Of Developing Class Diagrams
	is a kind of model
	only models things that will actually be implemented
model	becomes the core of documentation describing the system
	is crucial in software development
	is used to describe a software system
	is used to validate a software system
	see also model^2
	should be understandable by clients and users so they can participate in the development process as much as possible
	should be properly reviewed
	should provide abstraction so that not all details are visible at once
	should provide insights about the system when software engineers analyze it
	should use a standard notation such as UML so that everybody who looks at it will interpret it the same way

Next model: use case model    Up: model    Previous model: system domain model