Computer Information System - Case Study Example

Computer information system (Business Analysis) CIS assignment By Name To Name Date Institute Table of Contents Section 1 2 Question 1 2 Question 2 5 A- Dialog 5 B- Payroll system 5 C- Testing software 6 Section B 7 Question 1 7 A-Event table 7 B- Use Case diagram 9 Use Case Diagram 9 C- Domain Class Diagram 10 Question 2 11 A- Use Case [registration of a shareholder] 11 B- User Interface 14 14 C- Design Class diagram for the ‘Shareholder class’ 15 References 16 Section 1 Question 1 In this scenario we have to settle the argument on the establishment of the design of architecture for a new standalone system that will be used to manage projects across the organization. Satzinger et al has stated the structural system design and architectural frameworks that allow and provide guidelines regarding the set of programs should be developed, the main task that we need to accomplish. Here in this structural system design technique we develop a Structure Chart that provides us a basic system development scenario regarding the effective implementation. Here we implement the main principle of the program modules those are loosely coupled and highly cohesive. Satzinger et al has also discussed about the Object-Oriented Approach system design approach and development. Through this technique we views development information systems as set of working together objects that work jointly to achieve jobs. Satzinger et al has also stated the CASE tools based system development scenario. These tools support effective system design and development for the better system implementation. Here we have main argument is on the architecture for the new system. The first argues for a Web Services Architecture while the second argues for a Three-Layer Client/Server Architecture. In this system we have to implement the better online security system regarding the better establishment of the safe online data transmission and sharing. In this architecture we have to incorporate effective and well established client server architecture. Here security establishment is more critical because this architecture is accessed through the corporate Intranet. This situation can produce a save area of the system access level between client and server level. This division of levels will establish a restricted access to the organizational resources. Here we will incorporate the administrative and user password safe accounts those will effectively provide the safe resource sharing and accounts management. Web Services Architecture effective implementation is really essential for the better online services and data sharing among the organizational personals. This services architecture will provide the better online resource sharing and facilities for the approximately twenty project managers. This architecture need to incorporate the physical resource sharing and data movement among all online clients. In the online system we have danger form the data hackers and spamming. In this case the establishment of network firewall is really effective. This firewall will protect the system form the outside access and inside illegal intrusion. In the scenario of three Layer Client/Server Architecture the basic aim is incorporate fool proof security architecture that will ensure illegal data access. The three layer security architecture will incorporate the three levels of the information security, data access and resource sharing. At each level of system security we will have different access level and privilege level. The main areas or first level will be for the administrative tasks. This level will provide the better allocation of resources and accounts management. Next at the second level we will provide access to the main and higher rank project managers and organizational executives. This access level will have the privileges for the more enhanced data sharing and resource usage. This level will be more privileged as compared to least level of the access. Question 2 A- Dialog In this scenario of the user and system dialog we need to implement the short and more informative dialog for the better and interactive interaction. In the under discussion system and user dialog there the long sentences and line those give the feeing of distraction. Then we have to place the main check statement first for the exit or proceed. Here system process the all instructions and at the end gives the “transaction violated” message for exit. In this scenario the time of user and system wastes and this is against the better user infarction rules. In this case we need to provide a list of available products from where user can select the category and product. In this way long dialog can be minimized and also provide the better product information because user can type and name wrong that is not recognizable for the system. B- Payroll system In this system we need to establish a two level privilege system that will have an distractive and client levels. The administrative side will be used by the supervisor or any high official. The client level will be used by the data-entry clerk. This level will only provide the privilege for the data entry. The data changes can only be done at the admin level. This is more suitable way for the preservation of the correct data integrity. Here main controls we will require regarding the viewing the worker information. Here we will require a worker id against that we will establish a data table for the that user. This record will be used for the calculation of the working hours and wages. Here we will need to incorporate the constraints regarding the data type, length and correctness. C- Testing software In the process of testing software developed using top-down we will first check for the user interface error, then we will conduct unit testing, the next process will be combined system testing. After we will carry out the exhaustive testing that is also called the full load testing. In the bottom up testing scenario we start testing software for the combined unit levels. Here we will test for the combined system levels. At these levels we will find out main and big errors in the system working. After resolving errors we will goes towered the unit and user interface levels of the system testing. Satzinger et al has sated that the testing of the system is taken place in each state of the system development life cycle. Like in the system design stage we design the system and test for the better system implementation. Here we plan for the system unit testing to ensure that whole system can be implemented in an effective way. In the stage of the high level system design we develop the system tests. The basic aim behind these tests is to ensure the better and error free system implementation. As Satzinger et al has stated we test for the overall system behavior. This behavioral testing is carried out to ensure the appropriate system implementation. For this we build smoke test that is carried out daily for the assessment of any problem. According to Satzinger et al Here we also carry out performance test confirmation tests and time-based requirements analysis for the better system analysis and performance. The acceptance test is also carried out for the determining if the system meets user stated requirements. Section B Question 1 A- Event table Event Event Type Trigger Source Activity/Use Case System Response/Output Destination Registration through head office/phone/Web E User request for Registration Growers, Employees and Private people Shareholders Registration Assign unique shareholder number Growers, Employees and Private Monthly newsletter issuance E Issue of this newsletter Registered Shareholders Monthly newsletter issuance Records the latest prices for cane and the current shipping costs Registered Shareholders Purchase of Shares E Shareholders may purchase from many different brokers Brokers Purchase of Shares from Brokers Recording new purchase information about shares and share holders Brokers Issuance of certificate to stockholder T purchase shares Registered Shareholders Issuance of certificate Compile Email certificate Registered Shareholders Dividend payments request E Dividend payments request by Registered Shareholders Registered Shareholders Dividend payments Calculation of Dividend amount Registered Shareholders B- Use Case diagram Use Case Diagram C- Domain Class Diagram Question 2 A- Use Case [registration of a shareholder] Introduction This use case is about the Detailed Description to use case of the “registration of a shareholder” for those shareholders registering via the Web. Here I will elaborate the use case in more depth. Main Events This use case will contain the following main events: 1. Start 2. Open website of “Australian Sugar-cane Growers Association”. 3. Select for the “registration of a shareholder” option. 4. Provide user information 5. Specify the shares types 6. Specify the shares quantity 7. Payment 8. Registration number issuance for the shareholder 9. Exist Primary Stockholders Growers Employees Common people Secondary shareholder None Success Condition If the user properly provides the user information, then system requires the shares details on properly entering that system will ask for payment through the credit card number. When user enters the correct number and pays for the shares then system issues registration number. Failure Condition In case of wrong information, wrong credit card number system will no proceed and due to incorrect information system fails to proceed. B- User Interface Registration Of A Shareholder Via The Web Figure 1 User Interface C- Design Class diagram for the ‘Shareholder class’ Shareholder registration Register() Add_Record() Delete_Record() Save_Record() Check_Record() Employ -Emp_ID -Job type References 1. Alavi. 1984. An Assessment of the Prototyping Approach to Information System Development. Communications of the ACM, (p. 27). 2. Anderson, S. D. 2004, Project quality and project managers. Int. J. Proj. Manage , 10, 138-144. 3. Bailey, P. J. 2009, Out of Sight, Out of Sync: Understanding Conflict in Distributed Teams. Organization Science, Vol. 14, No. 6 , 615-632. 4. Baskerville, & Stage. 1996, Controlling Prototype Development through Risk Analysis. MIS Quarterly, (p. 20). 5. Carcone, P. 2008. Information Technology System Implementation. Retrieved 24 05, 2009, from Online Magzine and Writer's Network: http://www.suite101.com 6. Enterprise resource planning. 2009, Retrieved 24 05, 2009, from Wikipedia, free encyclopedia: http://en.wikipedia.org 7. Hofmeister, C., Nord, L. R., & Soni, a. 1999, Describing software architecture with UML. in Proceedings of the TC2 1st Working IFIP Conference on Software Architecture (WICSA1), (pp. 145-159). San Antonio, TX, USA. 8. Laudon, K. C., & Laudon, J. P. 1999, Management Information Systems, Sixth Edition. New Jersey: Prentice Hall . 9. Lori Rockett, J. V. 1998, Technology and virtual teams: using globally distributed groups in MBA learning. Campus-Wide Information Systems , 174-182. 10. Martínez-Normand, L. 2007, Software Accessibility Standards. Retrieved 05 18, 2009, from ADENU: http://adenu.ia.uned.es/workshops/um07/tumasa07/proceedings_UM07_TUMAS_A.pdf 11. Monk, E., & Wagner, B. 2009, Concepts in Enterprise Resource Planning, 3rd.ed. Boston: Course Technology Cengage Learning. 12. Pressman, R. S. 2001, Software Engineering: A Practicioner's Approach, 5th Edition. London: McGraw Hill. 13. Richards, H. 2004, Soft Systems Methodology. Retrieved April 14, 2009, from http://www.ifm.eng.cam.ac.uk/dstools/control/softsm.html 14. Selic, B. 1999. UML-RT: A profile for modeling complex real-time architectures. New York: ObjecTime Limited. 15. Satzinger, JW, Jackson, RB & Burd, SD 2007, Systems analysis and design in a changing world, 4th edn, Course Technology, Cambridge, MA. 16. Sommerville, I. 2004, Software Engineering, 7th Edition,. New York: Pearson Education (Addison Wesley). 17. Summers, J & Smith, B 2006, Communication skills handbook: how to succeed in written and oral communication, 2nd edn, John Wiley & Sons, Brisbane. 18. Tecnodiscap, G. 2004, User Modelling in Ambient Intelligence for Elderly and Disabled People. Retrieved 05 18, 2009, from Glyndŵr University: http://www.newi.ac.uk/groutv/papers/umaiedp.pdf 19. Williams, B. 2005. Soft Systems Methodology. Retrieved April 14, 2009, from Actrix Users Home Pages: http://users.actrix.co.nz/bobwill/ssm.pdf Read More