Monday, May 16, 2011
Why Requirement Analysis ?
To develop quality software – on time and on budget – that meets customers’ real needs. Project success depends on good RAM.
Saturday, May 7, 2011
Software Requirment
What Is Requirement ?
q A capability that the system must deliver
q A capability needed by the user to solve a problem to achieve an objective
What requirement Are Not ?
q project planning information
q design or implementation details or
q testing information
Why Requirement Analysis ?
The earlier in the cycle the defect is corrected
q Cost
q Delay
q Profit
q Customer satisfaction
q Customer confidence
Type of Requirement
Business Requirement
Business requirements represent a kind of "why" information. It represent the high level of objectives of the organization or customer who requests the system. Business requirement why the organization is implementing the system. Vision and Scope statement record the business requirement.
User Requirement
requirements constitute one type of "what" information. User requirements describe what the user will be able to do with the product, such as goals or tasks that users must be able to perform. Use cases, scenarios, user stories, and event response tables are some ways to represent user requirements.
Functional Requirement
Functional requirement specify the software functionality that the developer must build into the product to enable the user to accomplish their business requirement . Functional requirements represent one kind of "what" information. The traditional "shall" statements that describe what the system "shall do" or what the system "shall let the user do.“
System Requirement
Describe the top level requirement for a product that contain multiple subsystem that is a system. A system can be all software or it can be both software and hardware.
Components of requirement Engineering
Entire Software requirement Engineering domain is split into requirements development and requirements management.
Requirement Development
The purpose of requirement development is to produce and analyze product and product component requirement. The goal of requirements development is to identify, agree and record a set of functional requirements and product characteristics that will achieve the stated business objectives.
Requirement Management
The purpose of requirement management is to manage requirments of the projects products components and to identify inconsistencies between those requirments and the project’s plan and work product.
The central purpose of requirements management is to manage changes to a set of agreed-upon requirements that have been committed to a specific product release. Requirements management also includes tracking the status of individual requirements and tracing requirements both backward to their origins and forward into design elements, code modules, and tests.
Thursday, May 5, 2011
Soft Skills of a Business Analyst
An effective analyst combines strong communication, facilitation and interpersonal ability with technical and business domain knowledge and the right personality for the job.
Listening
Interviewing and Questioning.
Analytical
Facilitation
Observation
Writing
Organization
Modeling
Interpersonal
Creativity
Business Analyst’s Tasks
•Define Business Needs
•Identify Project Stakeholders and User Classes
•Elicit Requirements
•Write Specifications.
•Model the Requirements
•Lead Validation
•Facilitate Prioritization
•Manage Requirements
Responsibility
•Prepare Vision and Scope Statement
•Identify Project Stakeholders and User Classes
•Elicit Requirements
•Prepare Requirements Specifications(SRS)
•Decompose highlevel business and user requirements into functional requirements
•Define Quality attributes and nonfunctional requirements
•Lead requirements analysis and verification
•Requirement prioritization
•Peer reviews and inspections
•Requirements traceability and track
•Change Management
•Reuse requirement
•Assist product management
Software Business Analyst Skill Required
The Business Analyst(BA) is the individual who has the primary responsibility to elicit ,analyze, validate, specify, verify and manage the real needs.
Skill Needed:
Interview Skills
Listening Skills
Analytical Skills
Facilitation skills
Observational Skills
Writing Skills
Modeling Skills
Interpersonal Skills
Knowledge Needed:
Understanding Requirements Engineering
. Requirements Engineering Practices
Product management concepts
Application domain knowledge
Subscribe to:
Posts (Atom)