Documente Academic
Documente Profesional
Documente Cultură
A - Unified Modeling Language (UML) is the industry-standard language for specifying, visualizing,
constructing, and documenting the artifacts of software systems. Using UML, programmers and
application architects can make a blueprint of a project, which, in turn, makes the actual software
development process easier.
Q - Do I really need UML? Can't I just describe how my application is designed using
regular words?
A - While it's certainly possible to describe interrelated processes and code architecture in words,
many people prefer to use a diagram to visualize the relationship of elements to one another. UML
is a standard way to create these diagrams. As a result, it makes it easier for programmers and
software architects to communicate.
Q - What does a Collaboration Diagram (or Sequence Event, depending on the process)
model?
A - A System Event's behavior.
Q - In a Class Diagram, what does a line with an arrow from one class to another
denote?
A - Attribute visibility.
• Planning - This phase is where the objectives, alternatives, and constraints are
determined.
• Risk Analysis - What happens here is that alternative solutions and constraints are defined,
and risks are identified and analyzed. If risk analysis indicates uncertainty in the
requirements, the prototyping model might be used to assist the situation.
• Engineering - Here the customer decides when the next phase of planning and risk
analysis occurs. If it is determined that the risks are too high, the project can be
terminated.
• Customer Evaluation
a) The new system requirements are defined in as much detail as possible. This usually involves
interviewing a number of users representing all the external or internal users and other aspects of
the existing system.
b) A preliminary design is created for the new system.
c) A first prototype of the new system is constructed from the preliminary design. This is usually a
scaled-down system, and represents an approximation of the characteristics of the final product.
d) A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype in
terms of its strengths, weaknesses, and risks; (2) defining the requirements of the second
prototype; (3) planning and designing the second prototype; (4) constructing and testing the
second prototype.
e) At the customer's option, the entire project can be aborted if the risk is deemed too great. Risk
factors might involve development cost overruns, operating-cost miscalculation, or any other
factor that could, in the customer's judgment, result in a less-than-satisfactory final product.
f) The existing prototype is evaluated in the same manner as was the previous prototype, and, if
necessary, another prototype is developed from it according to the fourfold procedure outlined
above.
g) The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.
h) The final system is constructed, based on the refined prototype.
i) The final system is thoroughly evaluated and tested. Routine maintenance is carried out on a
continuing basis to prevent large-scale failures and to minimize downtime.