Children Support Agency System - Essay Example

Detailed Specification Children Support Agency System By Executive summery The emerging need for the better organizational management and overall processes handling makes its vital to implement an organizational information management system. The implementation of the efficient information management system makes it possible to handle the overall organizational tasks efficiently. Children Support Agency is a national charity based in the UK that cares for young people who require additional support to help them live their lives successfully. This organization has decided to implement a new information management system that will have the ability to manage the overall organizational information. The purpose of this report is to elaborate the system design features for its better implementation. Introduction The Children Support Agency (CSA) has emerged as a national charity based organization for the betterment of the UK’s young people. This organization has aimed to facilitate young people of UK for their career and support them for spending their lives effectively. Children Support Agency (CSA) has defined its 4 main areas of the work those are: Housing Family support Education & training Tackling crime CSA has developed their setup very effectively and they have their central office in London. Recently they have moved their two main offices, a small one in London and a larger one on the South Coast of England in Brighton. In this situation this organization has running lot of projects on diverse domains, for the management of these projects and better information transfer in the overall organization structure is really essential. There is need of some distributed information management system that is able to handle the overall organizational information and have the capability to tenser the data and information to each client. Section A Analysis of Semiotic Framework (i) CSA has initiated the development of the central information management system that will help the head office to monitor projects. The system will offer the effective tools to help regional directors, area managers and lead workers to manage their work. At the heart of the system will be the recording and monitoring of key performance indicators (KPIs) for each of the projects managed by CSA. Each department at head office should be able to see information as it relates to their department. Equally, the Regional Directors will need to see the data for their region, Area Managers for their area and Team Leaders for their project. This report will analyze the main system requirements and present the main design development initiatives. Kind of activities This section will provide the deep insight into the kind of activities for this project to the developer. The developer first analyzes the project requirement. Then he will sort out the workable requirements. After that the developer will draw out the basic system development requirements. This process will facilitate in the better system development. The developer will select a particular area of the system functionality and try to implement that area first. In this way developer will start the overall project development. (ii) In the system requirements analysis phase, the system development will be a part of this requirement gathering phase. This will provide developer a better overview of the whole project development. In the design stage the developer will involve to find out the better system development solution. In our project the developer will be combined with the design team to help them in the better and workable system features. The system coding will be the basic responsibility of the system developer. Here he will code the system for the implementation for all system requirements. The testing phase will be the combination of the system developer and testers. In this level the developer will help the system testers for the better system testing and error handling and fixing. (III) This section will provide a deep insight into the issues got by the system developer during the system development. In this project the developer can face a problem regarding the on going system changes. The business requirements vary from time to time. It is really difficult for the system developers to cope those errors. These problems can create the system problems regarding the end system deployment. In the system network analysis the developer has to implement the overall data distribution in all the company offices. This can be due to the complex data sharing and information handling on the overall company network. The development of company network will help to reduce the oval cost of the data transfer and travel cost. Now there will be no distance among the 70 Km apart office, this will help to reduce the cost of the physical data transfer among these office and the people who need to travel for the consultation on any project. So it will be really feasible to implement this technology. Section B – System requirements specification System requirements We are going to develop an information system that will offer the better user and project handling support through the corporate intranet. This project will enhance the overall organizational working performance. In this section I will present the different project development requirements. Functional requirements Usability Adaptability Ease of use Better performance User support Robustness Effect sharing of data on the company over company network Better information transfer over company network Non-functional Requirements Hardware LAN Equipments Computers (Pentium 4) Network Switch Servers Operating system (WIN XP, WIN XP-Server) Safety requirements The company data must be safely transfer Virus protection for business data Spy-ware protection for business data Hacking protection for business data Rich Picture Section B- Soft Systems Analysis using Rich Pictures CSA Information management system Quality control Project Progress Details New CSA system Program manager Regional Directors CSA Project team Design analysis System analyst Developer New system Multi user request processing System tester Order shipment System user Legend Figure: Rich picture of RapidDel problem situation Use Case Diagram Use case is a way that is scenario-based and used to measure the requirements. And Use case diagram is used to represent the use case (Sommerville, 2004). This section will present the main system responses regarding effective systems handling and management. Use case modeling for requirements analysis Here the use case diagram will show the main components of the system that are the system users (actors), response of the system, and relationship among the actors and use cases. According to the given case study of ‘Children Support Agency (CSA) System’, there will be following actors of the system. Main Actors: Director Regional Directors Area Managers Team Leaders Lead Workers Services Director Director of the Finance Use cases (primary) View organization projects details View project details at regional level View and analyse project information Check project progress Add resources Record and monitor performance indicators (KPIs) Contracts management and handling Use case diagram Error: Reference source not found Subscription Request Check project progress Sn Account Renewal Information Error: Reference source not found Use case index Use Case ID Use Case Name Primary Actor Scope 1 View organization projects details Director Regional Directors In 2 View projects details at regional level regional level regional level regional level Regional Directors In 3 View and analyse project information Regional Directors, Area Managers In 4 Check project progress Team Leader In 5 Add resources Team Leader, Finance Director, Lead Worker Services Director In 6 Record and monitor performance indicators (KPIs) Area Managers, Team Leader Team Leaders In 7 Contracts management and handling Lead Worker, Team Leader In Investigation The use case of the “View and analyse project information” is really essential use case that engages lot of different processing. Like in this use case we have to retrieve the whole project information and view the whole events running there. First in this use case we are going to view the project status and analysis. In the status report we will view the project current resources, its completion percentage and project phases. This information will provide a deep insight into the overall project scenarios and associated steps. In the analysis of the project, we be able to have the lot of tools those will facilities us to have the better project analysis and management. In this analysis we will make available to the project planning, resource management and assessment tools. Developing Primary scenario In the use case “View and analyses project information” the Regional Directors and Area Managers will request the system for the project analysis task. In this scenario there are lots of events that are involved. These events are explained below: USE CASE Regional Directors, Area Managers Purpose For the analysis of project task and phases Actors Regional Directors, Area Managers Type Primary Main course description Steps Actions 1. 2. 3. 4. 5. 6. 7. 8. 9. Open the main system interface Provide the log-in and password Search for the undergoing projects. Access the main project progress report Analyze the project Success scenarios Apply analysis tools and techniques Check results Save new adjustments Exit Notes Secondary scenario There are few secondary scenarios that are involved in system working. In the table below these secondary scenarios will be explained Alternative course description Step Branching action 3a. 3b. On the wrong password or user name the system will deny the access to the system In case of project completion this will be added to complete projects list. If a project is present in the completed projects list, then this will be no longer available to the current development projects. Notes Main system events: 1.1 User password authentication (assembly code) 1.2 Analysis system request processing (Project_Code_Id, Pick_date) 1.3 Project Processing (Resource_list) Alternative course system events: 1.3.a View details (Project_Id) 1.5.a Poejct-progress_details (Projetc_Stage_Id, assembly code) In this scenario the project data analyzer view the whole project, details and their associated resources. The project details will be available through entering project id. In this project we can set project resources by the project resource list. These resources can be settled and managed through the project resources availability list. Use case: Record and monitor performance Main course of actions: Children Support Agency (CSA) system will facilitate in the “record and monitor performance” of project. In this use case the main scenarios are given below: 1- User will open the main menu 2- Then the user will provide the password and user name 3- On the proper authentication the system will show the main project manus 4- The user will provide the project id to view to project details 5- Then user will analyze the project progress and further resource allocation details 6- This project screen will allow to analyze the project progress parameters 7- Save new added resources and close the application Alternative course of actions: 2a. System will stop the further working till the antiquation of user password and username 3a. Assign resources 7a. View another project Thanks   In the use diagram who (actor) is observing or communicate with use case (view and analyze project information)   Use case diagram (page 10) and Use case Index (page 12) it is not match with actor and use case. According to your use case index (actor and use case) it is not matched in the diagramQuality business management is one of the main business exceptionality of the 20th century. It has added a thoroughly stranded outlook to compact by means of imperfections in fabrication, focused deliberation on clients, as well as decorated participative organizational carry out in business. For this reason the Children Support Agency has initiated the information management system development that will facilitate in better information management and handling. The implementation of this infrastructure will add more flexible working environment and efficient problem handling, for each corporate predicament that is faced by the business organizations are seeking to diminish fixed costs-the costs that come off the bottom line of the business. There is also a drive to renovate fixed costs to variable costs wherever this is potential, pushing these costs out to the cost centers where they are incurred. This is giving rise to a surge in interest, on the element of huge organizations, in third-party sites or neighborhood offices, which can be accredited to definite cost centers (Berry, 1996). The accomplishment of the teleworking infrastructure will be able to diminish the amount of capital tied up in office facilities and the resources these facilities require for maintenance (Christine et al, 2000). This implementation will raise the on the whole organizational productivity as well as the better user support and handling. Here the user will be able to obtain new technological and effective facilities for the online transaction and product (plant) searching. By this way their awareness regarding the better services will be increased. In this system requirement analysis stage I have used the use case for the system requirements assessment. This section is aimed to discuss the main features assignment of the requirement analysis tools. Use cases Use cases are used to measure the system reaction in opposition to some input (Sommerville, 2004). This response turns out to be system functionally in the system design part. Use case covers mainly the system stakeholders and their associated tasks for the system response assessment. Use case is a very effective tool for the system functionality description assessment. There is biggest advantage of this method is facility to access the overall responses of the system for the effective system development. In this system developments use case outlined the main system responses and their interaction with the particular user. This way of information representation will facilitate in the effective system mapping and requirements exaction. Another advantage of use case is its facility to intricate the overall system negative response. This facilitates the developer and designer to manage the system in a better way. But at the same time we also have few disadvantages of this technique of information modeling and requirements analysis. For instance, for a complex system the representation of system response becomes very complex to show (Sommerville, 2004). Rich picture The next system requirements analysis technique which I have used is the rich picture. This is also called the soft system methodology. This way of requirements analyses is also an effective way for the requirements assessment. The main benefit of the rich picture is its capability to make out the main soft problems like that the human movement in addition to communication in the system (Avison & Fitzgerals, 2003). I have developed the rich diagram that openly addresses all the issues regarding system interaction and their connection to particular stakeholder. This image elaborates the structure of actor interactions with the existing application and the new feature. Here we also have facility to view the feature and their integration with existing functions. Rich picture provides a better way to demonstrate the vital fundamentals of the process flow. We can inspect the environmental factors as well as types of requirements that will have to be developed (Avison & Fitzgerals, 2003). The main advantages of rich picture are the facility to proffer a better understanding of the benefits: regarding the regions of disagreement, assets, concerned parties and their roles. Another facility of this tool is to demonstrate the ideas, thoughts, concerns, reactions and response of the system information and data. Rich picture also encounters few problems regarding its limitations in drawing and analyzing the basic system requirements and functionalities. Here we did not find any distinct rule or policy for the development of the rich picture. For this reason we are not able to have a standard way of system representation. The next main drawback is the powerlessness of this method to make obvious the multifarious system requirements and association (Avison, 2003). Conclusion In this report I have presented a detailed analysis of the Children Support Agency which is a new project for development of information and resource management system. This report has outlined the main system requirements and their system accusation. I have presented the overall system features and their requirements implementation for better system working and development. The developer’s role and tasks were also part of this discussion and in this way: we are able to get a better overview of the system development phases. References 1. Avison, D E, & Fitzgerals, G. 2003. Where now for development methodologies? Communication of the ACM. pp. 78-82. 2. Bass, L., Clements, P. and Kazman, R., 2003. Software Architecture in Practice, 2nd Edition. Addison Wesley, Reading, MA, USA 3. Christine Hagn, Wemhard H. Markwitz, 2000. Mobile Teleworking: Some Solutions and Information Security Aspects, Siemens AG, Information and Communication Products, Information Security, pp- 322-325 4. David E. Markby, 2000. Integrating teleworking into the organization, Telecommuting Management Consultants, P-167-169. 5. Horace Mitchell, 2003. Telework, Teletrade and Open Electronic Networking, IEEE, pp.1-3 6. Kenneth. C. Laudon. 1999. Management Information Systems, (Fifth Edition), New Jersey, Prentice-Hall. p. 334 7. Mens, T. Demeyer, S., and Janssens, D. 2002. Formalizing behavior preserving program transformations. In Proc. Int’l Conf. Graph Transformation, volume 2505 of Lecture Notes in Computer Science, pages 286–301. Springer-Verlag. 8. Miroljub Grozdanovic, Sonja Pavlovic Veselinovid, 2001, Framework for Teleworking NiS, IEEE, pp.723-726. 9. Nierstrasz, O. 2006. Software Evolution as the Key to Productivity?, University of Bern, Switzerland, pp.102-110. 10. Proper, H. and Weide, T. v. d. 2004. EVORM - A Conceptual Modelling Technique for Evolving Application Domains. Data & Knowledge Engineering, 12: pp. 313–359. 11. Selic, B, 1999. UML-RT: A profile for modeling complex real-time architectures. ObjecTime Limited. 12. Simon Berry, 1996. Teleworking Today, IEEE, pp.1997-2002. 13. Sommerville, Ian. (2004). Software Engineering (7th Edition). Addison Wesley. p. 176 Read More