A.2.2.1Describe differing IT requirements within given organisational scenarios
A.2.2.2
A.2.2.2
Describe appropriate matches between organisational need and IT
A.2.2.3
Compose a technology impact statement within a given situation
Plan Knowledge Area
Module A, Plan, looks at organisations and their use of IT, both as an enabler for effective Information Systems and as a platform for innovation. The module requires the candidate to have thorough understanding of organisations, their strategies and their business processes, as well as the global trends and opportunities which are involved. The candidate shall recognise the main issues related to the management of IT, such as selecting the appropriate technology, or choosing between in-house systems development or outsourcing. The candidate shall also be able to justify IT investments and know about some of the legal and ethical aspects of IT. He / She shall be aware of the requirement for a professional approach to project management and quality assurance. The candidate shall also appreciate the importance of team building and effective communication when presenting the case for change within the organisation.
Subscribe to:
Post Comments (Atom)
1 comment:
IT Requirements definition
What is IT requirements management?
IT requirements management is the translation of business requirements to an operational IT system. Where system development is required, your role as the customer is:
to ensure that your requirements have been correctly specified in consultation with users
to ensure that providers understand what you want
to monitor progress and any changes in requirements
to ensure that users (or their representatives) are involved in prototyping and development of the user interface
to check that the delivered system meets business need.
This briefing explains your customer role and outlines the development process from a customer perspective.
Why is it important?
Whether your IT requirements are to be developed in-house or outsourced, all the activities up to the production of a specification of business requirements are your responsibility as the customer. Many information systems development contracts assume it is possible to know what the requirements are at the start, and that is possible to produce a specification that unambiguously expresses the requirements. For all but the simplest systems this is rarely true. Requirements analysis is an iterative process; the system requirements will change during the period the system is being developed. It will require user involvement throughout the development process. You will also need to be aware of the implications for fixed-price contracts and change control.
System development is complex and subject to rapid change. You must consider the advantages of modular or incremental development, perhaps with more than one provider; you will be responsible for deciding on an appropriate customer/provider interface.
You must also be aware of the implications of the cost of maintenance when the system is in operation. Requirements will change during the life of the system and maintenance costs can be a major component of the total cost of ownership.
Key factors for success
Key factors for success are:
close consultation and involvement with users to ensure that their needs really will be met and that the new system will support the proposed processes
willingness on both the customer and provider side to work collaboratively
scrutiny of provider plans throughout the procurement process; this is essential in ensuring that objectives are delivered.
You must pay particular attention to ergonomics and human factors; if users do not like the system they will not use it. Usability criteria should be incorporated into requirements and design documentation. You must also consider special user needs, such as disabled users, circumstances of use, novice/expert users.
Who is involved?
Roles involved in IT requirements management include:
managers within the customer organisation responsible for defining the contract roles and deliverables
end-users of the system (or their representatives, where appropriate - eg representing the citizen)
customer/provider analysts involved in a joint requirements capture exercise
customer/provider managers concerned with:
- managing the contractual relationship
- provision of requirements
- quality control
- audit
- testing against business needs.
Post a Comment