Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Assignment 3-Requirement Techniques

Assignment 3-Requirement Techniques

Ratings: (0)|Views: 609|Likes:
Published by Sugandh Wafai

More info:

Published by: Sugandh Wafai on Dec 27, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Musarrat NawazReg # 0771126SSREAssignment 3Difference between JAD and QFDS.NoJADQFD
JAD is not quality-centered, butmore communication-focused.JAD expects improving thecommunication processes willresult in higher product qualityQFD is "an overall concept that provides a meansof translating customer requirements into theappropriate technical requirements for each stageof product development and productionthe customer must be able tovisualize the product as they aredirectly participating in it'sdesign
QFD, the customer is seen solely as a source of inti initial requirements.JAD is user centred designQFD is quality centred designJAD need directlycommunication with user QFD doesn’t need direct communication with theuser.To use JAD, the customer has to be able to visualize the softwaresince they participate directlyThis isn’t necessarily true for QFD.Joint Application Design is goaldrivenQuality Function Deployment (QFD) tries toapply the concept of total quality management tosoftware developmentQFD results in documented requirements
Both the JAD and QFD approaches use group session techniques, however they are onlya component of QFD. As with any group session approach, they both require facilitatorsto make the team interactions successful. As well both concentrate on customer involvement during the RE stages of the project
Both are group session techniques
Both require facilitators
Both require the project team to work with the customer 
JAD differs from QFD in that it is not quality-centered, but more communication-focused.JAD expects improving the communication processes will result in higher  product quality. QFD on the other hand, makes quality an explicit goal, rather than a byproduct of the process.
Unlike QFD, JAD is specifically designed for the development of large computer systems. The goal of JAD is to involve all stakeholders in the design phase of the product via highly structured and focused meetings. Typical participants in the
session include a facilitator, end users of the product, main developers, andobservers.
In the preliminary phases of JAD, the requirements-engineering team is taskedwith fact finding and information gathering. Typically, the outputs of this phase,as applied to security requirements elicitation, are security goals and artifacts. Theactual JAD session is then used to validate this information by establishing anagreed-upon set of security requirements for the product.
Allows key users to participate effectively
When properly used, JAD can result in a more accurate statement of systemrequirements, a better understanding of common goals, and a stronger commitment to the success of the new system
More expensive and can be cumbersome if the group is too large relative to thesize of the project
Guidelines for successful JAD
Use experienced and skilled facilitators
Get Executive sponsor’s commitment and support
Get the right person to participate
Set clear, well understood and obtainable goals
Plan detailed agenda and stick with it
Define deliverables clearly in advance
Keep technical jargon to minimum
Produce final document quickly
Roles in JAD
Session Leader (Facilitator)
Expert at and committed to the process
Excel at group processes (forming, norming, storming, performing)
 Needs to be trained – first choice, not last
Ensures comments, issues, facts, decisions, questions are recorded(verbatim where possible)
Excels at the tools – CASE, Word
Active participant – seeking clarity on wording and meaning
User Representatives
Must have knowledge, authority, experience
Good listener 
IT Representatives
Good listener 
Contributes technical information
Executive Sponsor 
Pays the bills
Makes the final decisions on issues
Selecting an Executive Sponsor
Right personality
Strong influence in the organization
Must have authority to make decisions
 Not afraid to make decisions
Selecting a Facilitator
Must be impartial
For system development project, the facilitator ideally comes from neither the user area nor the programming department.
Ex. IBM’s concept called the Development Center or place JADstaff in a group separate from IS.
Communicate well
Lead groups
Selecting a Scribe
Good working knowledge of the business area
Good analytical skills
Expertise in JAD documentation tool
Good notes taking skills
Good technical writing skills
Clear handwriting
Selecting Participants
Commitment is essential
It’s a balancing act
Want enough people to have full representation and decision power in allareas but at the same time must keep the session small enough to be productive.
For systems development project, a suggested ratio is five users to two IS people.
Selecting Observers
Should not be involved in any of the decision making
Allow them to answer questions, but nothing more.
Muzzle them completely.
Five Phases of JAD
1.JAD Project Definition2.Research

Activity (8)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
austatyra liked this
nkeshishi liked this
Zaran Tech LLC liked this
razak24434 liked this
ahdswd liked this
Marawele liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->