System Design of Botany Bay Surf Lifesaving Club System - Case Study Example

Table of Contents Table of Contents 2 Executive Summery 4 Introduction 4 Analysis of problem/Problem Situation 4 Purposed System 5 Scope 5 Main Features of System 6 Simple navigation system 6 Consistent 6 Keep the interface and content clear and simple 6 Effectiveness 6 Reliability 7 Affordance 7 Qualitative evaluation of usability 7 Design issues 7 Cognition 8 Colour 8 Recognition cues 8 Icon metaphor 9 Perception 9 Working Team 9 Project Budget 10 Project Time 10 Project Work Break down Structure 10 Risk Management 11 Question 2 14 BOTANY BAY SURF LIFESSAVING Club project contracting 15 Plan purchases and acquisitions: 15 Plan contracting: 15 Request seller responses; 15 Select sellers; 15 Contract administration; 16 Contract closure; 16 SECTION 2 16 Question 1 16 Event Table 16 Question 2 17 Use Case Diagram 18 Question 3 20 Class Diagram 20 Question 4 21 Design Class Diagram 21 Bibliography 22 SECTION 1 Executive Summery This report will present a detailed analysis of the system development for the BOTANY BAY SURF LIFESAVING Club. Here I will try to analyze and design the system that will provide the services regarding the management of the information and data for the Botany Bay Surf Lifesaving Club. Introduction In this age of modern technology the development and implementation of the Business Information System for every organization is really necessary. Information system provides a great help regarding the management and handling of the business information and data. Botany Bay Surf Lifesaving Club management has decided to develop and implement a new system that will manage and record all events regarding Botany Bay. This system is going to enhance the overall working power and Bay handling. Analysis of problem/Problem Situation The old working system is manual. The management of the overall data and its handling is really difficult through that system. Here we have paper based working environment that demands heavy duplication and extra resources for the data saving and handling. Here we have no current availability of information and working status at all centers. Purposed System The purposed system will be a digital and automatic system for the management and handling of the Botany Bay Surf Lifesaving Club. This system will provide the effective data storage and retrieval against and database query. Here new system will comprise the following modules of the data: Club members Finance committee Lifesaver member Members Event roster Scope This new system for Botany Bay Surf Lifesaving Club will provide an enhanced working and management structure. This will be a complete databases system for the Botany Bay daily events and working. This system will record the activities on the beach, records of the lifesavers, record of any incident on the beach and beach management record. Through this system Botany Bay Surf Lifesaving Club will effectively manage and handle the overall working data and daily record of the beach events. Through this record the overall management of Botany Bay will become easier and efficient. Main Features of System In the purposed system we will demand the following given system features regarding its feasibility regarding overall working and handling of the organization: Simple navigation system In this scenario we have tried to make the system easy to navigate among the different system section and modules. Consistent We have made the system consistent throughout the development. This consistency is regarding the system interface design, cooler scheme and navigation criteria. Keep the interface and content clear and simple We have tried to make the system easy to use. For the clarity of the overall contents of the system is really essential. These make the system easy to use, handle and manage. Effectiveness The system development is providing the better user support and functionality regarding the better system calculations and assessment. In this scenario we have tried to implement the accurate system calculations regarding the assessment of the transactions. Reliability The implementation of this system is more reliable because the development of this system has followed strict way of system testing and assessment. Affordance The system that we are going to develop should be more affordable, like we have used Visual Studio 2008 for the overall development. This is a extensively available tool that facilities us in a better way regarding the overall system development and implementation. Qualitative evaluation of usability The usability assessment provides a better way of system development and designing. Through this study we ensure that all main functionalities has implemented. There better implementation of the there functionalities ensures the easy working, effective system handling, better user interface and accurate outcome. Design issues In this section I will present the detailed analysis of the main design issues regarding the effective system implementation. The system designing is backbone in the development of each system. In our system design we have followed a compliance way for the overall system designing and management. In the section below I will discuss about the main design issues and there implementation. Cognition Main aim behind the better user interface design is its effectiveness regarding less complex interface. In this scenario we have to reduce the main memory work load of the user. This makes the working of system for the user easier. The feel of closure is really necessary for the system user. For this we need to reduce the main memory workload and provide less complex user interface. In this way the user interface becomes more effective and easy to use for the overall tasks. For this purpose we have tried to provide hints and on click help regarding each aspect of the system functionality. Colour The selection and implementation of the light colors is really necessary. The utilize of the dark and distracting color schemes makes the overall user interface more complex and un-workable, so we have used the light color scheme and made it consistent thought the application development. Recognition cues In this scenario we have developed a consistent user interface. The use of similar pages, frames, buttons and other user interface items. This gives the feeling of similarly and after one or two time use the user able to familiar with the system. We also tried to make the system less complex regarding the overall working, so it seems easier to work with this system and manage the overall system working and tasks. Icon metaphor The use of proper and consistent Icon metaphor through out the application was our main priority regarding the overall application development. This makes our system more useable and easy to work with, in scenario of more similarity and less distracting feeling. Perception In this system design we have tried to capture the user and client perception regarding the effective systems design. Here we have tried to implement the system in a way that client/user has suggest. This make the user feel more effective when he/she uses the system. Working Team For this project we have following staff for the overall system development and implementation; Project manager Programmers Business analyst Here we will need a staff of two programmers; a business analyst with limited technical knowledge and the two programmers are technically strong and have worked on maintaining the council's financial package for many years. Project Budget This project will cost $ 20000 budget. We have to implement this project within this allocated budget. This budget will include the project team resource cost, development system cost, consultation cost, implementation cost and other costs regarding the electricity and facility of life. Project Time We have got time of three months for this system development and implementation. This time is enough for the overall system development. I have divided this time to other activates of the project implementation. Here each activity will take a specified and pre allocated time for the completion of the job. No. Project Activity Allocated Time 1 Requiems 15 2 Analysis and design 15 3 Coding 30 4 Testing 15 5 Implementation 15 Project Work Break down Structure Here I have developed the overall project work break down structure. This will demonstrate the overall activities regarding this project development and implementation. Risk Management This section is about the BOTANY BAY SURF LIFESSAVING Club risk analysis. This section will present a detailed analysis of the main risk events are there mitigation plan for the risk minimization. RISKS LIKELIHOOD Probability of occurrence ASSUMPTIONS RESPONSE Compliance with acquisition laws (Internal) Medium Acquisition laws are clear and complied Establish strict organizational ethical policies Social barriers in the area Low Resistance unlikely Social barriers are tackled through customer and vender friendly business policy Regulatory barriers Low Laws are unambiguous Regulatory barriers can be resolved by establishing a well suited organizational ethical policy Increased intensity of competition in technology Medium Attractive industry invites high and unexpected competition We have enhance our credibility regarding beach services Obsolescence in technology Low It is assumed that the technology we are implementing becomes obsoletes Here we have adopt the technology that can fulfill the all aspect of new technology implementation Specialist attrition (Internal) Low Adequate talent pool is not available in the organization We have to establish better recruitment plans Infrastructural risks (non availability of power, working system, internet, etc.) Low System develop require sufficient resource Try to establish more backup plan so that in lack of one resource we can use the alternative Quality of product Low Quality of beach management system is really essential Implementation of the ISO specified standards Timely Delivery of project Low Penalty for time overruns incorporated in the contract We have establish well suited time line and the strict obligations for its fulfillment Cost overrun in project Medium Protected in the contract Better and effective cost plan never results in cost overrun. So need for the best quality cost plan. Cost overrun – Operational costs (internal) Medium Wage negotiations are periodical. Selection of the human power (workforce) should be according to need of project Quality of design (Internal) Medium Adequate s/w engineering strengths resident in the company Design is backbone of any project so we have to establish more enhanced and quality design Uncertainty of cash-flows during project implementation Low Volatile economy Better and effect cost plan can manage such risks Question 2 BOTANY BAY SURF LIFESSAVING Club project contracting This section is about the process of the contracting among the BOTANY BAY SURF LIFESSAVING Club and nine vendors. Here we will adopt a standard way of contracting among both stakeholders of the project. The section below contains the overall process of the contracting for this project. Plan purchases and acquisitions: This is the first process in which we will determine the development of the MIS for BOTANY BAY SURF LIFESSAVING project related needs and plan for the development process. Plan contracting: Next step in this Procurement process is the process of getting and establishing the requirements for MIS project and services that will be needed by our project team for the MIS construction and lab establishment. Request seller responses; In this stage of the system development process we will identify a list of vendors to that have the ability provides us required MIS and services. Select sellers; In this phase we will select vendor that will provide the MIS product or service. The project team may make the final an ultimate choice, though normally inside an overall procedure that is owned by the Purchasing Department. Contract administration; In this phase we will manage the relationship with the contracted company by which they will provide us MIS and services. Contract closure; This happens if the contractual association existed simply for the life or completion of this project. SECTION 2 Question 1 Event Table destination System response/ output Activity/ use case Source Trigger Event type Event Table Common person Person registration joining the club Common person User request E joining the club General members members registration for committee joining the committee General members of Botany Bay Surf Lifessaving club General members request E committee establishment lifesaver member Registration Number issuances Registration for lifesaver member Common person Common person request E Registration for lifesaver member General members Payment receipt Annual subscription payment General members General members of club E Annual subscription payment General members and Lifessaving club system roster development system roster development General members and Lifessaving club incident may occur during at beach E system roster development Question 2 Use Case Diagram Reqt. For lifesaver reg. Reqt. For lifesaver reg. Question 3 Class Diagram Question 4 Design Class Diagram Figure 1 Design Class Diagram Bibliography 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