Object Oriented Software Engineering   View all facts   Glossary   Help

subject > person or group > person > stakeholder > software developer > modeller > architectural modeller

architectural modeller
subject			fact

architectural modeller	is a subtopic of 9.4 - Software Architecture
	is a kind of modeller
	performs architectural modelling
	refines architectural model by following these steps iteratively: Sketch an outline of the architecture, based on the principal requirements and use cases. Determine the main components that will be needed, such as databases, particular hardware devices and the main software subsystems Refine the architecture by identifying the main ways in which the components will interact, and by identifying the interfaces between them. Decide how each piece of data and functionality will be distributed among the various components Consider each use case and adjust the architecture to make it realizable Mature the architecture as you define the final class diagrams and interaction diagrams
	should apply design principles
	should avoid circular dependencies among packages
	should make the interface of a package as simple as possible to simplify its use and testing
	uses UML diagrams
software developer	asks several evaluators to independently perform heuristic evaluations
	develops software
	has goal rewarding career, recognition, or the challenge of solving difficult problems or by being a well-respected 'guru' in a certain area of expertise
	is part of software development team
	maintains software
	may be judged on when they deliver product, not on its quality level
	may be reluctant to develop new libraries, APIs and frameworks because developing anything reusable is seen as not directly benefiting the current customer If a developer has painstakingly developed a high-quality reusable component, but management only rewards the efforts of people who create the more visible 'final product', then that developer will be reluctant to spend time on reusable components in the future Efforts at creating reusable software are often done in a hurry and without enough attention to quality. People thus lose confidence in the resulting components, and in the concepts of reuse and reusability
	may refuse to reuse components in which they lack confidence
	most often works on custom software
	must ensure that the set of use cases is complete and that they are expressed consistently and unambiguously
	must inform the project manager about any problems
	must understand the customer's business environment, their problems and the available technology which can be used to solve the problems
	often fails to adequately involve users in the development process
	often has significantly less knowledge about modelling than about design and programming
	often underestimates software development time because it is very hard for people to assess the quality of software or to appreciate the amount of work involved in its development
	reuses libraries and APIs delivered with a programming language
	should be rewarded for developing reusable components
	should emphasize the use case or use cases which are central to the system, which represent a high risk because of problematic implementation, or which have high political or commercial value
	should identify all the use cases associated with the software product
	should not document a design only after it is complete
	should not omit design documentation
	should only reuse technology that others are also reusing
	should realize that attention to quality of reusable components is essential so that potential re-users have confidence in them
	should realize that developing and reusing reusable components improves reliability, and can foster a sense of confidence
	should realize that developing reusable components will normally simplify the resulting design, independently of whether reuse actually occurs
	should work for several months on a testing team; this will heighten her awareness of quality problems she should avoid when she returns to designing software
	wants software that is easy to design and maintain and which has parts that are easy to reuse
stakeholder	must agree on requirements

Up: modeller