Sunteți pe pagina 1din 2

Software Engineering Resources

Risk Analysis and Management:

Risk analysis and management are a series of steps that help a software
team to understand and manage uncertainty. Many problems can plague of
software project. A risk is a potential problem; it might happen, it might
not. But regardless of the outcome, it's a really good idea to identify it,
assess its probability of occurrence, estimate its impact, and establish a
contingency plan should the problem actually occur. The following topic
categories are presented:

Analysis Modeling:

The written word is a wonderful vehicle for communication, but it isn't


necessarily the best way to represent the requirements for computer
software. Analysis modeling uses a combination of text and diagrammatic
forms to depict requirements for data, function, and behavior in a way that
is relatively easy to understand, and more important, straightforward to
review for correctness, completeness and consistency. This section
presents resources for conventional and object-oriented analysis (OOA)
methods as well as resources for UML.

Analysis modeling is an extremely robust subject. This set of resources


has been organized into the following topic areas:

Software Design Engineering:

Design is a meaningful engineering representation of something that is to


be built. It can be traced to a customer's requirements and at the same time
assessed for for quality against a set of predefined criteria for 'good'
design. In the software engineering context, design focuses on four major
areas of concern, data, architecture, interfaces, and components. In this
section, we present design engineering resources that address:

Software Testing Strategies:

Designing effective test cases (see Software Testing Techniques) is


important, but so is the strategy you use to execute them. Should you
develop a formal plan for your tests? Should you test the entire program as
a whole or run tests only on a small part of it? Should you rerun tests
you've already conducted as you add new components to a large system?
When should you involve the customer? These and many other questions
are answered when you develop a software testing strategy. The following
topic categories are presented here:
Software Testing Methods:

Once source code has been generated, software must be tested to uncover
(and correct) as many errors as possible before delivery to your customer.
Your goal is to design a series of test cases that have a high likelihood of
finding errors - but how? That's where software testing techniques enter
the picture. These techniques provide systematic guidance for designing
tests that: (1) exercise the internal logic of software components, and (2)
exercise the input and output domains of the program to uncover errors in
program function, behavior, and performance. Resource presented in this
section address the following topic categories: