School of Computing / Skool vir Rekenaarkunde - Name
School of Computing / Skool vir Rekenaarkunde - Name
School of Computing / Skool vir Rekenaarkunde - Name
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
53<br />
INF305F/ SWE401I/SED401I /101<br />
The questions that must be asked and answered are given on page 138 <strong>of</strong> prescribed<br />
textbook. Relate each <strong>of</strong> the questions to the registration system.<br />
Why is the system being developed? In this activity the development team should assess<br />
the validity <strong>of</strong> business reasons for the changes. In the registration system, there should be a<br />
good reason for a new system that justifies the changes. For instance, a reason may be to<br />
improve slower hand-processes to be able to get a higher throughput <strong>of</strong> registrations.<br />
What will be done? For this question, it is necessary to identify the functionality to be built<br />
and, by implication, the tasks required to get the job done. If the goal is to create a new online<br />
registration system with electronic payment facilities, the development team will typically have<br />
to include tasks such as negotiation with financial institutions to accommodate the<br />
transactions, and identification <strong>of</strong> team members that will develop the interface for payment.<br />
Similarly the remaining questions must be answered and related to the registration system,<br />
including the following:<br />
- When will it be accomplished?<br />
- Who is responsible for a function?<br />
- Where they are organisationally located?<br />
- How will the job be done technically and managerially?<br />
- How much <strong>of</strong> each resource is needed?<br />
5 What are the types <strong>of</strong> requirements in quality function deployment within a<br />
university registration system? (6)<br />
The requirements are discussed in detail on page 188 <strong>of</strong> the textbook. The requirements<br />
include normal requirements, expected requirements and exciting requirements. For each <strong>of</strong><br />
the requirements it is necessary to relate the requirements to the registration system. For<br />
example, in normal requirements that reflect objectives and goals stated for a product or<br />
system during meetings with the customer, the customer (user <strong>of</strong> the registration system in<br />
this case) may comment on interfaces built by the team, test registration functions such as<br />
the electronic payment, and remark on how efficient a new registration is done.