1 Comment

1. 

   AYESHA MUMTAZ on February 8, 2019 at 5:11 pm

   Q1: Who are stakeholders?  Software engineers  System end-users  Managers of system end-users  External regulators  Domain experts
   Q2: Input/output of RE Processes?
   RE Process – Inputs:  Information: It include the information about the functionality of systems to be
   replaced and the Information about other systems, which interact with the system
   being specified
    Stakeholder needs: Description of what system stakeholders need from the
   system to support their work
    Organizational standards: Standards used in an organization regarding system
   development practice, quality management, etc.  Regulations: External regulations such as health and safety regulations, which
   apply to the system
    Domain information: General information about the application domain of the
   system
   RE Process – Outputs:  Agreed requirements: A description of the system requirements, which is
   understandable by stakeholders and which has been agreed by them
    System specification: This is a more detailed specification of the system, which
   may be produced in some cases  System models: A set of models such as a data-flow model, an object model, a
   process model, etc., which describes the system from different perspectives
   Q3: What are the major objective of process improvement?
   Process improvement is concerned with modifying processes in order to meet
   some improvement objectives Improvement objectives which are; Quality
   improvement, Schedule reduction, Resource reduction. Q4: What are the role of different actors in RE process?
   Actors in the RE Process  Requirements engineering involves people who are primarily interested in the
   problem to be solved (end-users, etc) as well as people interested in the solution
   (system designers, etc.)  Another group of people, such as health & safety regulators, and maintenance
   engineers may be effected by the existence of the system
    Role-action diagrams are process models which show the actors associated with
   different process activities  They document the information needs of different people involved in the process  They use model of prototype software system as part of requirements elicitation
   process
   Q5: Which stakeholder should be part of review team?
   Review Team Membership
    Reviews should involve a number of stakeholders drawn from different
   backgrounds. People from different backgrounds bring different skills and
   knowledge to the review. Stakeholders feel involved in the RE process and develop
   an understanding of the needs of other stakeholders  Review team should always involve at least a domain expert and an end-user
   Q6: What impact of wrong requirements?  When requirements are wrong, systems are late, unreliable and don‟t meet
   customers needs  This results in enormous loss of time, revenue, market share, and trust of
   customers
   Q7: What are the change management polices and it stages?
   Change Management Policies  The change request process and the information required to process each
   change request  The process used to analyze the impact and costs of change and the associated
   traceability information
    The membership of the body which formally considers change requests  The software support (if any) for the change control process
   Change Management Stages  Problem Analysis and Ch
   engineers, because they consider that to be obvious and implicit  Errors of clarity and ambiguity: Second most common errors are those of clarity
   and ambiguity. Primarily, because natural languages (like English) are used to state
   requirements, while such languages are themselves ambiguous. For example: object  Errors of commission: Errors of commission can also find their way into the
   requirements documents  Errors of speed and capacity: Performance, that is errors of speed and capacity, are also found in requirements. Primarily, these occur due to conflicting
   understanding or competing needs of different stakeholders
   Q10: What are the key issues between client organization and requirement
   team?  Financial arrangements  Ethical obligations  Legal safeguards  Personal relationships  Denial of information
    Management of changes
   Q11: What level of capability maturity model?  CMM Level 1 – Initial: Organizations have an undisciplined process and it is left to
   individuals that how to manage the process and which development techniques to
   use
    CMM Level 2 – Repeatable: Organizations have basic cost and schedule
   management procedures in place. They are likely to be able to make consistent
   budget and schedule predictions for projects in the ame application area
    CMM Level 3 – Defined: The software process for both management and
   engineering activities is documented, standardized and integrated into a standard
   software process for the organization
    CMM Level 4 – Managed: Detailed measurements of both process and product
   quality are collected and used to control the process  CMM Level 5 – Optimizing: The organization has a continuous process
   improvement strategy, based on objective measurements, in place