system Comparison Table

Object Oriented Software Engineering View all facts Glossary Help

Next subject: test Up: subject Previous subject: symbol

system comparison table

Subject make use of have design for be turn into is a synonym of is a subtopic of have example become produce undergo have purpose divide perform have benefit develop as specify has definition divide up into automate develop using contain combine

distributed system vulnerable to privacy invasions of its users by gathering data about people as they use network-based programs or by actively intercepting communications 3.4 - The Client-Server Architecture A system in which computations are performed by separate programs that co-operate to perform the task of the system as a whole clients and servers

object oriented system abstraction in order to help make software less complex in a state until an event occurs that causes it to change state 2.2 - Classes and Objects subsystems procedural abstraction with data abstraction

prototype in a state until an event occurs that causes it to change state the final system since it will be hard to maintain, and will contain many bugs pilot system 4.6 - Some Techniques for Gathering and Analyzing Requirements early to get a view of potential problems to gather requirements by allowing software engineers to obtain early feedback about their ideas any computations it is easily modified many times in response to feedback from users A version of a system created primarily to learn more about the requirements, and not intended to be the final product subsystems a rapid prototyping language part of the system's eventual functionality

safety critical system its requirements subjected to rigorous analysis and review in a state until an event occurs that causes it to change state 4.7 - Types of Requirements Document systems that control industrial processes, vehicles, telecommunications networks, medical equipment and many consumer devices if it could jeopardize safety or the environment if it fails subsystems

software system well-described requirements if other systems or subsystems are going to use its services or communicate with it flexibility right from the start better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors 1.9 - Difficulties And Risks In Software Engineering as a Whole complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features evolution over its life-span in many ways:
A distributed system is divided up into clients and servers
A system is divided up into subsystems
A class is divided up into methods
a prototype subsystems business process

subsystem in a state until an event occurs that causes it to change state 9.1 - The Process of Design A system that is part of a larger system, and which has a definite interface one or more packages

Next subject: test Up: subject Previous subject: symbol

Subject	make use of	have	design for	be	turn into	is a synonym of	is a subtopic of	have example	become	produce	undergo	have purpose	divide	perform	have benefit	develop as	specify	has definition	divide up into	automate	develop using	contain	combine
distributed system				vulnerable to privacy invasions of its users by gathering data about people as they use network-based programs or by actively intercepting communications			3.4 - The Client-Server Architecture											A system in which computations are performed by separate programs that co-operate to perform the task of the system as a whole	clients and servers
object oriented system	abstraction in order to help make software less complex			in a state until an event occurs that causes it to change state			2.2 - Classes and Objects												subsystems				procedural abstraction with data abstraction
prototype				in a state until an event occurs that causes it to change state	the final system since it will be hard to maintain, and will contain many bugs	pilot system	4.6 - Some Techniques for Gathering and Analyzing Requirements			early to get a view of potential problems		to gather requirements by allowing software engineers to obtain early feedback about their ideas		any computations	it is easily modified many times in response to feedback from users			A version of a system created primarily to learn more about the requirements, and not intended to be the final product	subsystems		a rapid prototyping language	part of the system's eventual functionality
safety critical system		its requirements subjected to rigorous analysis and review		in a state until an event occurs that causes it to change state			4.7 - Types of Requirements Document	systems that control industrial processes, vehicles, telecommunications networks, medical equipment and many consumer devices									if it could jeopardize safety or the environment if it fails		subsystems
software system		well-described requirements if other systems or subsystems are going to use its services or communicate with it	flexibility right from the start	better at error handling if it effectively prevents the user from making errors, detects errors, and helps the user to correct errors			1.9 - Difficulties And Risks In Software Engineering as a Whole		complex because it is easy to add new features and because software engineers typically add features without fully understanding a system, which may not have been originally designed to accommodate the features		evolution over its life-span		in many ways: A distributed system is divided up into clients and servers A system is divided up into subsystems A class is divided up into methods			a prototype			subsystems	business process
subsystem				in a state until an event occurs that causes it to change state			9.1 - The Process of Design											A system that is part of a larger system, and which has a definite interface	one or more packages