EA Seminar '09
Introduction to Enterprise Architecture
By Mr. Ian Charters, IBM Distinguished Engineer and Architect.
EA needs to satisfy two distinct objectives – it must helping the enterprise do the right things , inspiring change that supports organisation's business strategy; while also helping to do things right , guiding the creation and deployment of business centric, often IT based solutions. In this session Ian will discuss how EA needs to be "much more than just an architecture" if it is to both guide and govern change…
To watch the full 20 min video, please login to Manageware free Knowledge-Center.
|
|
|
Back to top |
|
The Essential Software Requirement
Author: Karl E. Wiegers, Ph.D.
One problem with the software industry is the lack of common definitions for
terms we use to describe aspects of our work. Different observers might
describe the same statement as being a user requirement, software requirement,
functional requirement, system requirement, technical requirement, business
requirement, or product requirement. A customer’s definition of requirements
might sound like a high-level product concept to the developer. The developer’s
notion of requirements might sound like detailed user interface design to
the user. This diversity of definitions leads to confusing and frustrating communication problems.
What is requirements management?
Author: Jeremy Dick
This paper attempts to explore the nature
of requirements management.
The different tasks performed through requirements are
illustrated, in order to show the "requirements for requirements".
Requirements-Driven Testing
Author: Jeremy Dick
This paper outlines the benefits of
requirements-driven Testing
Author: Andy Gurd
With the dynamic nature of today's modern software and systems
development practices, it is no longer
possible to gather a complete set of requirements
specifications upfront and set them in stone for the
duration of the entire project. A far superior approach,
which more accurately reflects the development process,
is to allow requirements
specifications to evolve as the development project progresses.
However, this has created a seemingly unsolvable paradox
– how can projects accommodate myriad requirements
changes without spiraling out of control and still meet cost, quality
and time-to-market objectives? This paper looks at how to
solve this paradox and introduces the concept of Dynamic
Requirements
Author: Richard Watson
While Requirements Management tools have been successful,
to varying degrees, in representing the history of
requirements, there has been little or no attempt to provide
a record of relationships and their impact at previous milestones.
Traceability has always represented the relationships between
requirements in the present timeframe with little or no interest
in what was done in the past. This simplistic approach has been
compounded by the fact that Requirements Management
has left milestone definition to underlying configuration management
environments, therefore providing no direct relationship
between requirement and its related milestone. For the first time in
any requirements management tool, Telelogic resolves
the complex issues of relationships over time and their connection to
milestones with a collection of capabilities named
Intelligent Traceability.
Configuration Management
Configuration Management articles and papers
Guidelines for Evaluating a Change and Configuration Management System
Software development teams, challenged with producing
complex, high quality software products, often spend
too much time coordinating their development efforts.
These co-ordination challenges, along with increasing competitive
pressure and fast time-to-market expectations, have prompted
many organizations to look for better, more efficient ways to
manage development. Change and configuration management
technology helps organizations overcome these challenges.
The market offers many change and configuration management
products, from simple tool sets to global systems. With so
many solutions available, organizations need help deciding which
technology is the best fit for their needs.
In this paper, we will:
- Discuss the symptoms of poor change and configuration management,
- Provide an overview of the basic approaches for managing changes
in development,
- Introduce the distinct but interrelated components of a change and
configuration management system, and
- Suggest an approach to evaluating a change and configuration
management system.
Best Practices for Software Projects: Task-Based Configuration Management
Successful organizations have recognized Task-Based
Configuration Management as today's best practice,
providing them with a competitive edge in this area by
increasing developer productivity, equipping project managers with
powerful control over the content of their builds, and greatly
improving team communication and collaboration.
Component-based Development
Component-based development is creating applications
from reusable parts. This practice promises to
accelerate the delivery of software solutions with lower cost,
improved quality, and increased customer satisfaction. This
paper describes how IBM SYNERGY/CM provides a
framework and process for sharing components between teams or
individuals, thereby helping your company realize the
considerable benefits of component-based development.
Strategic QA: Steps to Effective Software Quality Assurance
This paper details the challenges and solutions
available for organizations wishing to improve their software
development process, reduce costs, improve quality and
increase reliability of planning. It also presents examples of
companies that have successfully implemented Strategic
QA and, as a result, have become more competitive.
