Term Paper: Software Engineering Outline Requirements

Pages: 7 (2030 words)  ·  Bibliography Sources: 1  ·  Level: College Senior  ·  Topic: Engineering  ·  Buy This Paper

SAMPLE EXCERPT:

[. . .] In other words, CAT output provides information for formal reduction strategy designs.

These formal reduction strategy designs can be used to eliminate such problems as reducing redundant classes or replacing unnecessary classes or inefficient subclasses with more efficient superclasses. Since the software design process is considered an iterative process, the goal of revising UML class diagrams with a CAT helps a software engineer evaluate and therefore reduce redundant coupling during the software design process and this entails the fact that less refactoring will be required once the software is in a production phase.

A second refactoring example is the use of the Rational Rose which is a UML-based CASE tool. Using a UML-based CASE tool to get the big picture for refactoring helps reduce risk or problems by the fact that each refactoring can be easily diagramed and evaluated so each small alteration visibly displayed can aid in reducing risk. By using a case tool there is an added benefit of the system always remaining fully functional during and after any minute refactorings. This again is an added opportunity to reduce the chances that a system is inadvertently thrown of whack or even seriously broken during a restructuring. CASE tools like Rational Rose tend to add more importance to the design phase and less stress later in the implementation phase. CASE tools permit the engineer to easily produce a diagram that express basic fundamentals and help to show where refactorings could be needed later on.

2.3

This section tries to explain what is wrong with the provided diagram above and also to propose a modification that would better solve the concern observed. In this example, a mirror hierarchy is demonstrated that occurs as two or more class hierarchies take on a similar shape because each model functions on a series of related concepts and certain factors standout to make the process better or worse. For example, considering each class hierarchy in isolation the overall process may make perfect sense but when considering the factors or classes as a group they may not work well together and therefore not make sense.

The assessment of this diagram is that equipment in turn defines the purpose of the lab. The problem is that a mirror diagram works on the premise that one should be allowed to substitute subclass occurrences for a superclass. In this diagram you could therefore assume that nuclear equipment could be used when and wherever equipment could be used. But, the problem is in the way the diagram was displayed. As is, one could not utilize the substitute factor or more specifically one could not use nuclear equipment within the nuclear lab for example.

Thus, a better solution would be to allow for the Chain of Responsibility factor to be built in where each subclass a tie to its responsible function. By redrawing the flow (see below) we could if necessary substitute subclass occurrences. Thus, we could allow for both laboratory equipment and nuclear equipment to be used whenever equipment is used and still allow for nuclear laboratory and laboratory to work together as needed.

References

Jamie Gregory - Email address: -- Order ID:… [END OF PREVIEW]

Sustainable Engineering Practice Role of Engineers (Computer Term Paper


Progress in Software Engineering Software Testing Term Paper


Software Recommendation Argot International Technology Solutions Term Paper


Human Factors Engineering Documented Evidence Term Paper


Operations Plan for Web Media Contents Monetization Software B2b Business Plan


View 167 other related papers  >>

Cite This Term Paper:

APA Format

Software Engineering Outline Requirements.  (2005, January 14).  Retrieved September 17, 2019, from https://www.essaytown.com/subjects/paper/software-engineering-outline-requirements/84061

MLA Format

"Software Engineering Outline Requirements."  14 January 2005.  Web.  17 September 2019. <https://www.essaytown.com/subjects/paper/software-engineering-outline-requirements/84061>.

Chicago Format

"Software Engineering Outline Requirements."  Essaytown.com.  January 14, 2005.  Accessed September 17, 2019.
https://www.essaytown.com/subjects/paper/software-engineering-outline-requirements/84061.