ASSIGNMENT 2 TO BE ABOUT
DEVELOPING AND IMPLEMENTING AN IT –BASED TRANSCATION PROCESSING SYSTEM
Remarks: take a screenshot of the system form and keep it in the report, even if it’s from the internet it’s fine
1. ASSIGNMENT TITLE
Developing and Implementing an IT-Based Transcation Processing System
This will present the background of the assignment, how, why, where and from whom it is initiated. This will include a brief organizational background where a system project will be developed including its business processes and operations.
3. ASSIGNMENT OBJECTIVE
This section defines the main and specific objectives of the system project.
4. SCOPE OF THE ASSIGNMENT
4.1 Project Management: Provide full project management for this assignment
The provider will have to present the following:
• Transcation Processing system
• Engage in a scoping and planning exercise
• Define the business objectives of the assignment
• Develop a strategy for meeting them.
The activities should include developing business and technology strategy, define the change imperative, building a business case, assess the change readiness, determine processes and system risk assessment, develop project team technical environment, and define overall training strategy.
4. 2 Designing the system
4.2.1 Defining the system
This will require the provider to formulate a clear statement which reflects a precise understanding of the scope and nature of a problem. Establishing a definition serves two purpose: it will commit the organization to developing an appropriate information system which will serve the needs of the organization and its stakeholders, and serves as a benchmark against which the system can be measured once it is operational. Defining a system requires the input and agreement by the organization and system developer.
4.2.2. Identifying reporting requirements
The provider should identify reporting requirements as the next procedure in building an information system. Unless it is done, it is impossible to know what data will eventually have to be collected. Particular attention must first be paid to recognizing all user groups. Developing proposals for reporting formats speeds up the process because stakeholders have something to respond to.
4.2.3 Specifying operational requirements
The provider will have to interview the end-users to note the operational requirements, and definitely before determining software and hardware requirements, and definitely before the system building procedure begins. The best source of operational requirements information is the Projects Office and the line function managers who will use the system.
4.2.4 Technical standards
The provider will be expected to define the under-mentioned technical standards that would begin the process of rationalizing technology and explain how they will work to enable the Project Management System to share data and inter-operate with other systems.
• Networking protocols
• Operating systems
• Data-bases and data-warehouse
• Transaction processing
• Desktop environment
• Multi-media standards
4.2.5 Identifying data elements
It is required that the provider transform the reporting requirements into data requirements or elements. This means deciding which pieces of raw data must be collected and processed in order to produce the reports requested by information users. The provider must identify data elements meticulously. Attention also need to be given to how the data is to be entered. As this procedure gets under way, related data elements should be grouped together in order to create data files.
4.2.6 Determining the equipment requirements
The provider will have to define the tools, supplies, machinery or materials which will be required to operate the system. Equipment could mean a certain software application running under specific computer operating system environment. It is however important to keep in mind that not all systems require essentially the latest technology to operate effectively.
4.2.7 Building the system
The procedure to be followed consists of three sub-procedures:
18.104.22.168 System design: the provider should lay a physical design of the system. It is required the relationships and dependencies are established between the groups of data elements, or data files, in order to determine how data files interact with each other. The result of this sub-procedure should be a schematic diagram which will be used to guide the system builder.
22.214.171.124 System development: The builder should use the design document to start the process of establishing what the data entry forms will look like, what data will be entered onto which paper forms; how the data will be entered; how output, in the form of reports will be generated.
126.96.36.199 Software set up: Install and configure the system to provide the required support to line functions. The provider will configure and pre-test the system to confirm that it supports the target vision, and define the required custom development work. Activities include designing the To-Be processes and technology requirements, configuring the processes in the software, creating the training curriculum, and developing technical specifications for conversion, reports and forms.
188.8.131.52 System testing: The builder should ensure that the system functions correctly. If errors are found the builder of the system must locate the source of the problem, repair it, and test it again. The builder should from time to time consult with Projects Office and line function managers to find out about the user’s impressions of the look and feel of the system.
184.108.40.206 Writing system documentation: the provider should document the procedure which have been followed as the system development proceeds.
Technical documents: The technical documents should describe in detail every aspect of the development process, from the point of defining the system through a detailed description of what went into the building of the system. No elements should be ignored –a detailed record of the work which has been done to date must be put down in writing. This will enable a new system builder to build on what a previous one has done.
User documents: A user document or manual is crucial. Many users may be at a complete loss when using a newly built system unless they can refer to a well-written user manual.
220.127.116.11. Implementation and Training: The assignment provider should validate and implement the integration of the new business processes, the software, production technology, processes and systems security and controls, and organizational infrastructure and workforce changes. Activities should include performing integration and end-user training, performing process and technology cutover activities for “go live’.
18.104.22.168 Project Review: The provider should outline an assignment review process
22.214.171.124. On-going Support and Maintenance: The provider should outline how on going support and maintenance will be offered.
5. DESIGN AND IMPLEMENTATION PHILOSOPHY
The provider should outline how he/she will conduct a joint needs analysis of specific requirements with the Projects relevant line functionaries. The core system to be tailor made to suit the needs of the organization’s business processes.
Concentrate on core requirements
Based on the results from the needs analysis, the provider should sequence the requirements and concentrate on core requirements
6. EXPECTED OUTCOME AND DELIVERABLE
• A fully functional Project Management System
• Customised Financial Management System
• A trained Programme for Users
• A customized projects office (front and back) in electronic format (CD)
• Technical documents
• User documents
7. COMPETENCY AND EXPERTISE REQUIREMENTS
Includes the providers qualifications as systems specialists and others.
8. SERVICES DESCRIPTION
• Project Management
• Software set up
• Customisation and Installation
• Implementation and Training
• assignment Review
• On-going Support and Maintenance
9. APPLICATIONS / FUNCTIONALITIES
9.1. Assignment’s Financial Management System
The system should be able to perform the following:
Assignment Earned Value Graph
Should be able to measure a series of categories and overall performance within an assignment.
• Measure assignment performance
• Planned Value, Actual Value, Actual Costs
• Monetary value to time and cost
• Forecast estimate to complete the assignment based on current performance