Defining Software Requirements

objectives | learning points | differentiators | content


Does This Sound Familiar?

  • "And then a miracle happens!"
  • "How can we produce usable systems specs – detailed enough to begin software design?"
  • "Projects just take too long."
  • "We’re spending too much time dealing with changes."

"How do you know you’ve captured and specified all the correct requirements?"


Get The Answers To:

Achieving Efficient Preliminary Design

  • A rapid development cycle maximizing the limited time and resources of the company

Identifying System/Software Specs Easily

  • With IT and business subject matter experts

Defining Complete & Correct Specs

  • Sufficient, accurate, & verifiable

Producing a Usable Spec

  • Completing a specification that’s ready to "Code and Go".

Best Business Requirements Practicesä

Uses Familiar, Proven Software Specification Methods and Best Practices.

  • A unique systematic method – compiled from the experts in systems analysis & design, and supporting industry standards from CMM, ISO and IEEE.

Defines a Clear and Easy Process

  • Finally there is a set of simple models, tools and techniques compiled in an easy to perform process – and conforming to standard specification formats – that takes you easily from Business Analysis to Systems Design.

Demonstrates a Proven, Applied Approach

  • That works on today’s projects. It’s not just re-hashed, conventional structured methods.
    We make best practices work!

Produces a high quality, industry standard Software Requirement Specification

  • A unique balance between rigorousness and simplicity. All within a framework defined by ISO, CMM, and IEEE.

    Correct § Ranked § Unambiguous § Verifiable § Complete § Maintainable § Consistent § Traceable

"I only wished that we had used this on our last project – it would have saved us a huge amount of time and effort."

 

Practical Two-day Workshop

Defining Software Requirements: Best Business Requirements Practicesä

A real-world course for new or experienced system analysts, designers and architects -- involved in legacy or OO system development, maintenance or enhancement projects.

This session runs through the path to producing good design building on the principles and concepts of Best Business Requirements Practices™ for Specifying Client Requirements.

The course is a mix of presentation, demonstration, and exercises. The same real-world case study is carried through the session resulting in a completed, detailed System Requirement Specification addressing the individual nuances of the participants.


Learn How To:

  • Use systematic techniques for specifying requirements – like use-case scenarios, process modeling, data modeling, object modeling and many others.
  • Easily transition from user requirements to a systems design specification.
  • Apply practical, proven analysis and design best practices—built on the framework and standards from IEEE, ISO and SEI’s Capability Maturity Model (CMM).
  • Document the system specification – documents, tools, whiteboard – using the latest methods, procedures, skills and techniques.
  • Produce complete, precise and concise specifications – ready to "Code & Go".

"This is the first time I’ve seen everything come together so clearly and easily – this will work in our shop. I’m really excited about it."


What’s Our Difference

  • Brings together proven, modern design principles and modeling methods.
  • It’s ‘how-to-do-it’—not just a comparison of methodologies.
  • It will work directly with your current methodology, tools and key practices.
  • A business user-centered method that specifies the system requirements from the perspective of the users’ domain of work – resulting in better design.
  • We teach it and we do it
    – seminar leaders are consultants with real on-going project experience.
  • Produces a specification faster & more accurately than any method available today –ensuring nothing is missed and it’s done right the first time.

Good design is about taking the user requirements and turning those business needs into a high quality software solution. The tough part of building today’s systems is not usually the coding but the architecture of the software design. The architect needs to understand the needs of the users of the product, and model those requirements in a ‘blueprint’ specification. That specification’s notation and language will be used by both the clients and contractors throughout the construction. It will also be updated with new requirements and/or design considerations and will be used to assess the quality and completion of the product.

That means it is critical that the process to perform this preliminary design be fast enough to meet time-to-market demands of the customer, simple and manageable enough for the architect or analyst to use, and strongly focused on the business user’s application of the product.

That’s why this approach employs the best methods and practices developed by the industry experts and used by leading consultants and companies. The Information Architecture Group has put together this unique framework and practices that quickly results in high quality ‘code & go’ Software Requirement Specifications not previously possible.


Course Content

Principles of the Best Practices for Specifying Software Requirements

Simplicity § Business user-centered § Time-to-market focussed "Objective"- oriented § Stepwise refinement § IT/User interactive Accuracy § Completeness § Clarity § Consistency § Verifiability § Maintainability § Testability § Traceability § Compliance

IEEE § SEI Capability Maturity Model § ISO Standardization efforts

Software Engineering concepts § Object/data-driven § Structured Systems Analysis & Design § Information Engineering § and others

Segmenting the Software Requirement Specification

Different partitioning methods and techniques. Identifying the activities, sub-systems, modules, patterns, components and their relationships.

Refining and reorganizing the Business Requirement Specification

Defining the Scope of the Project and Specification

Different partitioning methods and techniques. Identifying the activities, sub-systems, modules, components and their relationships.

Software Specification Methods and Practices

Modeling using tables, matrices, diagramming notations, textual specification language, cross reference tables, templates and worksheets.

Specifying the data requirements for the system. § Entity-relationship diagramming § Object modeling § Logical data model § Normalization theory simplified § The Data Dictionary § Object life cycles § Data usage

Specifying the functional requirements of the system. § Use-case scenarios § Data flow diagramming § Activity relationship model Structure charts § Specifying sequence § Workflow § Functional, component and key operation specifications § Event-response analysis State transition diagramming § Activity dependency diagrams § Decision tables § UML § Specifying Actors, Roles § Work Sessions

Specifying hardware & software architecture (non-functional) requirements.

Input/Output Specifications § User Interface Specification § Data Presentation Modeling § Prototyping

Documenting the Software Requirement Specification

Presentation § Format § Standards § What needs to be included § Tips



CONTACT US

1-800-209-3616

Copyright © 1997 The Information Architecture Group
and The Information Architecture Group, Inc. All Rights Reserved