Embedded Files
For internal use of KMB students only
Strand 3: IT systems
Introduction
All IT development requires a management method. Knowledge and understanding of the product development life cycle (PDLC) should be used as a framework to develop an IT solution for the internal assessment. It is recommended that this topic is covered before students start work on the project.
IT concepts to address in this topic
Theoretical fundamentals
Client, end-user, developer
Data collection techniques for content and product design, citing of sources
Role of testing and processes used
Technical and end-user documentation (manuals)
End-user training
The product development life cycle (PDLC)
Investigation of existing system(s)
Feasibility study
Requirements specification
Project schedule
Product design
Product development and technical documentation
Client and end-user evaluation
Practical techniques
Appropriate design techniques
Data capture
Product testing and debugging
teaching slides
teaching slides
Intro to Project Management - Teaching Slides ver 1.0.pdfASSESSMENT PRACTICE
Assessment objective 1: Knowledge and Understanding
Identify two stages of the product development life cycle (PDLC).
investigation of existing system
feasibility study
requirement Specification
project schedule
product Design
product development
prototyping
technical documentation
client and end-user evaluation
testing and debugging
Award [1] for identifying each stage of the product development life cycle (PDLC) up to maximum of [2].
Identify four ways that TecniCo could gather data about the present situation.
investigation of existing system
direct observation of business operations to identify data needed about requests, sales, products offered, clients
interview key stakeholders (business owner, employees and customers)
use questionnaires to survey key stakeholders (business owner, employees and customers)
analyse the current system/documentation to understand how records are kept.
Award [1] mark for identifying each way that TecniCo could gather data about the present situation up to a maximum of [4] marks.
TecniCo will provide a list of requirements for the solution proposed.
Identify two categories of information that should be included in the requirements specification provided by TecniCo.
system interaction
input and output requirements
processing requirements
security requirements
specific performance criteria
IT system requirements (hardware and software).
Award [1] mark for identifying each category of information that should be included in the requirements specification provided by TecniCo up to a maximum of [2] marks.
Assessment objective 2: Application and analysis
The Uber app was created using the product development life cycle (PDLC). Explain why the developers would have included a feasibility study, project schedule and user evaluation.
Feasibility study
this provides the project manager with an indication about whether the project is realistic (possible solutions, identification of end-users) the feasibility study may include an analysis of constraints such as cost, time required, technical expertise, IT infrastructure.
Project schedule
this provides the project manager with a possible timeline for the implementation of the app this will enable the project manager to have an overview of the respective tasks, how they relate to each other and potential pinch points in the development process.
User evaluation
this will provide the developers with first hand feedback about the performance of the app this will inform the developers of potential issues that may arise when the app is released and potential areas for improvement in the app.
Award [1] for explaining why a feasibility study, project schedule and user evaluation have been included and [1] for a development of the reason identified up to a maximum of [2].
Mark as [2] + [2] + [2].
The developers of ColegiumWise may accept requests from clients such as schools for additions or changes to the system. The developers send out system upgrades and updated user manuals on a regular basis with the changes that have been requested by the schools and other clients.
Explain three different ways the upgraded version of ColegiumWise could be tested before it is sent to the schools and other clients.
MIS is tested by the development team (in-house or alpha testing – system). Accept responses that detail specific tests, eg regression testing, unit testing, testing the correct operation of validation rules, etc
MIS is sent to a small number of schools and they are asked to try the new options (pilot/prototype, a part of agile development)
a “test version” or “beta release” version of the MIS is made available that users may try and send comments on what they find (beta testing).
NB: Candidates may detail the testing of more than one validation rule. Award marks for each different valid test explained.
Award [1] for identifying a way the system with the additions or changes may be tested before they send the upgraded version to the schools and [1] for a development of the way identified up to a maximum of [2].
Mark as [2] + [2] + [2].
Assessment objective 3: Synthesis and evaluation
ColegiumWise has several key functions that cannot be changed. The contract with the developers of ColegiumWise is due to expire in 2018 and the administrators at WHS have two options:
continue with ColegiumWise, knowing that it will not have the specific functions required by the school
not renew the contract and develop their own school management information system (MIS) for the school.
Evaluate these options.
Renew the contract
the ColegiumWise system is ready and can be used immediately as they have been doing
users are already familiar with the system and won’t require any retraining
support provided by the ColegiumWise provider
changes requested by other schools (clients) may be useful to the school (client) as well
school may have to pay a costly licence while the system is being used
school may need to adapt some features they wish to include to what is offered by the software
some changes requested may take too long to be implemented
there will be further need for additional features over time so it is likely that the current MIS will become increasingly limited in the future
the school may have to include data in the database which they don’t need but the system requires (which wastes their time).
Create their own
the system will be created to cover the school’s exact needs (if possible)
the system may be adapted to changes that are introduced over time
a team will have to be appointed for the development of the system
the in-house system may take a long time to be created
the school (IT team) has the responsibility of the functionality of the system
the school (IT team) has the responsibility for the security of the stored data
new staff may need to be hired as current staff may not have sufficient expertise to develop and support the system
there may be additional requirements for hardware to run the new system
may involve more costs for development and training
migrating data from the existing (ColegiumWise) system to the new system may cause issues (eg data loss, incompatible formats, data types, etc).
Page updated
Google Sites
Report abuse