Information Technology - Business Plan Example

Business Information Technology Task Business Process Model Task: 2 Requirements Catalogue Source: IST Ltd Priority: High User Responsible: Office in charge Requirement ID: R001 Functional Requirement: Customer Registration The customer registration form will be sent to the Head Office to be processed. The following details will be input into the system:- Customer ID Customer name Customer address and postcode Gender Date of birth Marital Status Customer Company Customer Position Customer Salary Non-Functional Requirement(s): Description: Target Value: Acceptable Range: Comments: Availability Access The availability would be round the clock as the system would be a web based system Records management is entirely with the IST Ltd, whereas the general access to the availability of the courses and checking ones invoice status can be done by the designated customers. Benefits: IST Ltd would keep all the requests of the customer and provide efficient solution towards customers and their services obtained. It would provide efficient system to invoice the customers and amend the booking status. Comments/Suggested Solutions: Related Documents: Business Process Model Related Requirements: Resolution: Source: IST Ltd Priority: High User Responsible: Office in charge Requirement ID: R002 Functional Requirement: Request for Courses The following courses attributes are taken into consideration: Courses Id Courses Name Courses Strength Courses Manager Courses Availability Status Non-Functional Requirement(s): Description: Target Value: Acceptable Range: Comments: Availability Access The availability would be round the clock as the system would be a web based system Records management is entirely with the IST Ltd, whereas the general access to the availability of the courses and checking ones invoice status can be done by the designated customers. Benefits: IST Ltd would keep all the orders in their central repository which can be only viewable for the customers and none would be able to change it. Comments/Suggested Solutions: Related Documents: Business Process Model Related Requirements: Resolution: Source: IST Ltd Priority: High User Responsible: Office in charge Requirement ID: R003 Functional Requirement: Booking of Courses The following booking information would be obtained for securing a booking for a course: Booking ID Booking Date Booking Clerk Name Booking Status  Booking status can be as follows: -------- Ready for Invoicing (This status is into effect only when the customer has added delegates and confirm that no more is to be added for the training) -------- Invoiced (This status is supposed to be for those who would have received the invoice details by the end of the month) -------- Paid (Only when the invoice is paid, the status is changed) -------- Completed (It is enforced only when the booking is confirmed as complete for a particular session of a course) -------- Course List Printed (It takes into effect only when the invoice is paid and final confirmation is reached) Non-Functional Requirement(s): Description: Target Value: Acceptable Range: Comments: Availability Access The availability would be round the clock as the system would be a web based system Records management is entirely with the IST Ltd, whereas the general access to the availability of the courses and checking ones invoice status can be done by the designated customers. Benefits: IST Ltd would keep all the booking information and would change the status effectively as per the invoice details and its association. Comments/Suggested Solutions: Related Documents: Business Process Model Related Requirements: Resolution: Source: IST Ltd Priority: High User Responsible: Office in charge Requirement ID: R004 Functional Requirement: Invoicing of the Customer The customer is invoiced for their courses: Invoice Id Invoice Status Invoice date Non-Functional Requirement(s): Description: Target Value: Acceptable Range: Comments: Availability Access The availability would be round the clock as the system would be a web based system Records management is entirely with the IST Ltd, whereas the general access to the availability of the courses and checking ones invoice status can be done by the designated customers. Benefits: IST Ltd would keep all the invoicing information and details of the invoices. The various information of the entire system would be collated and would produce reports accordingly. Comments/Suggested Solutions: Related Documents: Business Process Model Related Requirements: Resolution: Task: 3 Figure 1: DFD - Context Level Figure 2: DFD - Level 1 Task: 4 Logical Data Model Identification of Initial Entities Entity Key Customer Customer ID Course Course ID Booking Booking ID Invoice Invoice ID LDS Grid Customer Course Booking Invoice Customer X X X Course X Booking X Invoice Relationships First Draft LDS First draft of the LDS would appear to be like the following: As seen above in the LDS draft model, there is a certain many-to-many relationship that needs to be resolved for the final LDS. I will have to resolve the many-to-many relationship using link entities, so as shown below the relationship is resolved: Final LDS for IST Ltd Task 5 Relational Data Analysis: Course Booking UNF 1NF 2NF 3NF Booking Reference No Date Booking Clerk ID Booking Clerk Customer ID Customer Name Course Code Course Title Course Date Location Delegate Number Delegate Name Accommodation Booking Reference No Date Booking Clerk ID Booking Clerk Customer ID Customer Name Course Code Course Title Course Date Location Delegate Number Delegate Name Accommodation Booking Reference No Date Customer ID Customer Name Booking Clerk ID Booking Clerk Course Code Course Title Course Date Location Delegate Number Delegate Name Accommodation Booking Reference No Date Booking Clerk ID Booking Clerk Customer ID Customer Name Course Code Course Title Course Date Location Delegate Number Delegate Name Accommodation Task 5 Relational Data Analysis: Invoice UNF 1NF 2NF 3NF Invoice Number Date Customer ID Customer Name Customer Address Booking Ref Course Code Course Title Booking cost Delegate ID Invoice Number Date Customer ID Customer Name Customer Address Booking Ref Course Code Course Title Booking cost Delegate ID Invoice Number Date Customer ID Customer Name Customer Address Booking Ref Course Code Course Title Booking cost Delegate ID Invoice Number Date Customer ID Customer Name Customer Address Booking Ref Course Code Course Title Booking cost Delegate ID Task: 6 Events Creation: New Course Booking Modification: Course Delegate Recorded Modification: Delegate Added to Booking Modification: Booking Ready for Invoicing Modification: Invoice Issued Modification: Invoice Paid Modification: Delegate List Printed Modification: Course Completed Deletion: Course Completion + 3 Years Operation list: 1 -- Booking status changed to “Completed” 2 -- Booking status changed to “Invoiced” 3 -- Booking status changed to “Ready for Invoicing” 4 -- Booking status changed to “Course List Printed” 5 -- Booking status changed to “Paid” Modeling within SSADM is based upon three views of the system namely the structural view, logical view and the time based. All these are depicted above in the form of DFD, ELH and time based perspective of the system. All these are interrelated in a manner that it influences the basic form of the processing logic and enable better realization of the data flow and life cycle of the entity. It also denotes the composite nature of the logical structure and the basic flow of the system with respect to time. The deletion of the booking is kept with the system for 3 years and gets eliminated once the booking expires. Thus the timing is taken into account. References/Bibliography Curtis, G. and Cobham, C., (2005). Business Information Systems. 5th ed. London: Financial Times/Prentice Hall. Hoffer, A. Jeffery (2002). Modern Systems Analysis and Design, Pearson Education. Laudon, Kenneth (2002).Managing Information Systems: Organization and Technology, Fourth Edition. Pressman G. Roger (2003). Software Engineering, MH. Rajaraman (2002). Analysis, Design of Information system, Pearson Education. Sommerville, Ian (2004). Software Engineering, Pearson Education. Read More