1- You have been selected to participate on the systems investigation team for a
ID: 3581009 • Letter: 1
Question
1- You have been selected to participate on the systems investigation team for a new system in your area of the business. How can you contribute to the success of the effort? How might you use critical success factors to identify important system requirements?
2. You must approach one of the mid-level line managers in your organization and convince her to assign one of her key people to lead the system investigation phase of an important project. This phase of the project is expected to last three months and the individual will be needed fulltime during the investigation. What resistance do you expect from this manager? What counter-points can you offer to convince her to assign this person?
Explanation / Answer
Before project start-up, work is needed to establish the objectives and scope of the project.
It is necessary to establish the dimensions of the ‘triple constraint’ of time, cost and scope/product/quality.
Where the development work is to be undertaken by an external supplier, there may also be a process of tendering and negotiating a suitable form of contract for the project
Project Start-Up: Project Initiation Document; Project Plan; Quality Plan; Risk Management Plan; Configuration Management Plan. Note that these various plans may be combined into one document, especially for smaller projects.
Analysis of Requirements: Requirements Specification (covering the requirements themselves plus definitions of the processing and data requirements for the system).
Technical Design (include overall architecture of the proposed system, module specifications and database schema).individual modules combined together to create a working system.
Test results (from integration, system and acceptance tests) and an Acceptance Certificate from the users confirming that it meets their requirements as defined in the Requirements Specification.
In system testing, the developers are checking that the system provides the functionality defined by the users in the Requirements Specification.
As well as the developers and testers, the business or systems analysts may be involved here to look at the system from a user perspective.
Finally, the users are invited to conduct an acceptance test to check that what they have asked for in the Requirements Specification has been provided.Often,
the users require help from the business or systems analysts in performing these tests and the
The acceptance criteria should be derived from the Requirements Specification, which is where the users’ stated needs are documented.
The actual acceptance criteria may not necessarily be defined in the Requirements Specification, which might thereby become too large and unwieldy,
but it is important to make the requirements as specific and measurable as possible to avoid later arguments over acceptance;
for example, ‘a response time of less than 2 seconds for 90% of transactions’ is a lot more precise than ‘a fast response time’.
Since the acceptance criteria are based on the Requirements Specification, this emphasises the importance of that document.
Any project is a cooperative venture between the clients/users and the suppliers/developers and it is important that both parties have a clear understanding of what will happen,
when and what are their respective responsibilities. A process model provides a framework so that both parties can see where they will be involved and what their roles will be at each stage.
It also highlights the important milestones in the project and enables the stakeholders to plan their time so as to be available when they are required.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.