Asset Management Software Documentation - Essay Example

ASSET MANAGEMENT SOFTWARE DOCUMENTATION By The of the The of the School The Table of Contents 1.1 Project Initiation Documents 3 1.1.1The purpose and objectives of the new system 3 1.1.2 Stakeholders analysis 4 1.1.3The scope of the system 4 1.1.4Benefits analysis 4 1.1.5 Constraints of the project 5 1.2 Requirement Specification Document 5 1.2.1Choice of requirement gathering technique and justification 5 1.2.2 Conducting the RG exercise 5 1.2.3 List of all requirements for the new system 5 1.2.4 Use case description 6 1.3 Designing system functionalities using Data Flow Diagrams 7 1.3.1Context Diagram: including a description on what it is and what it shows 7 1.4.1What is ERD, and what is it for? 9 1.4.2 A description of ER model and any issues that need clarification 9 1.4.3 The ER Diagram. 10 1.5 System Architecture 11 1.5.1 Purpose of the architectural design? 11 1.5.2 The architectural design 11 1.5.3 Design notes 11 References 13 1.1 Project Initiation Documents The asset manager will be the precise tool for managing assets. It will have assets repository with a catalogue that has customizable standards. An intelligent automation system for the wok flow will be connected to the state transition panel/engine. This is a combination that will create the best environment and provide the best tools for you efficiently manage your assets. The main objective of this system would be to put you in a position that will promote your regulatory compliance, easily acquire your detailed reports and in a mighty way place you in a place where you will have a greater negotiating power with your contracts and vendors. This is a feasible project if we regard the obvious fact that business will be better and easier for you after the system is in place. The project costs are friendly; we are available for offering support and grow with you in your business endeavors and finally this system will help you avoid legal and also licensing issues. The software will have a web panel for accessing, inputting and managing data, and a design panel for the designing of the system. 1.1.1The purpose and objectives of the new system The new system will serve to help in the administration of your assets in a more efficient way. This will be achieved by the systems functions of; assigning forms, setting up items in the catalog, configuring workflows, auditing history etc. The system will also issue reports on contracts, vendors and assets amongst many other functions that will help automate and reduce data redundancy of the current system. The system will also make sure that the current value of the assets is clear and updated as frequently as possible by calculating frequently these assets amortization. 1.1.2 Stakeholders analysis Your business is big to you and others too. By this, I mean, the way you run the business affects you and other people who might not be affiliated to you directly. My study on the stakeholders proves that when you manage you assets well and efficiently, those who are directly in contact with the assets stand to benefit directly or indirectly. 1.1.3The scope of the system Your being a middle sized firm; I propose to do a simple system that will be a prototype and leave room for modification and upgrading as you progress and increase your assets base. The capacity of the system will be up to 800 assets. The system will have a user, system and data management capabilities. It will also generate reports upon request by the necessary administrator or user that has rights. 1.1.4Benefits analysis The benefits of proper assets management that will be brought about by the system include the fact that you will be better placed to make informed decisions that will have a positive impact on the firm. You will also be better placed to face the future knowing that there are no legal proceedings taking place that might limit your decision making as far as using the firm’s assets in progressing your investments is concerned. Better bookkeeping will be the norm in the firm where all the necessary documents will be well placed and saved. The invoices, maintenance records, inspection records etc. are quite important to the business. 1.1.5 Constraints of the project The biggest constraint of this project would be a negative attitude of the team towards the application and integration of the new system. This will only serve to work against the firm. Most end system end users never agree to the idea of a system upgrade. This is because it entails their shifting from their comfort zone and facing a challenge to learn new ideas and procedures. 1.2 Requirement Specification Document The users of the system are key in making sure that there is a well functioning system that is efficient enough. Thus information was needed for the actual building of the database and system architecture. I will gather information using surveys, questionnaires, onsite visits and interviews. I will then summarize my findings in one document and forward it to you so that you can approve the requirements. These I will use in the development of the system. 1.2.1Choice of requirement gathering technique and justification I chose to use observation, interview and questionnaires. These happened to be the ones that were most appropriate in this case. The staff was more than willing to fill the questionnaires and the management to grant me appointments that I may interview them. 1.2.2 Conducting the RG exercise I plan to concentrate on the questionnaires to gather information, as these are high data gathering and storage tools. They will also be easy to us when I will finally start tabulating my findings as I analyze the data. I plan to present the questionnaire to the team and also management of the firm. 1.2.3 List of all requirements for the new system According to the system requirements, the new system will need to have aspects like cancelation of a synchronization task that is in progress, the users will be able to filter the displayed lists based on characters that they will type and also the new system will have the ability to bulk update its database for check box controlled values. 1.2.4 Use case description Figure 1: Use Case Diagram 1.3 Designing system functionalities using Data Flow Diagrams Figure 2: Data Flow Diagram 1.3.1Context Diagram: including a description on what it is and what it shows 1 2 3 4 5 6 7 8 Figure 3: Context Diagram Key: 1 System updates the bank with the current records of the value of these assets 2 User keys in new acquisitions and makes requests to the system 3 The bank supplies the system with information on what financial advantages that business can get into because of their assets value and management 4 Tax department makes demands to the system to supply taxation records 5 The system requires information about the local authorities especially in regards to the state of the assets and where the assets are in a position likely to influence the environment. 6 The system supplies information that will be helpful to the local authorities. 7 The local authorities make demand to the system and business on whether the firm is following the local authorities’ regulation especially as far as managing assets is concerned. 1.3.2Level 1 Diagram. Figure 4: Level 1 Diagram 1.4 Modelling Data Requirements using Entity Relationship Diagram 1.4.1What is ERD, and what is it for? An Entity Relationship Diagram (ERD) is an organization’s graphical representation of its data storage requirements. It is an actual abstraction that tries to paint a picture of how the real world is (Ambler, S. 2006). 1.4.2 A description of ER model and any issues that need clarification Below is a sequence diagram for the asset management system. Figure 5: Sequence Diagram 1.4.3 The ER Diagram. Figure 6: Entity Relationship Diagram 1.5 System Architecture 1.5.1 Purpose of the architectural design? This architectural design serves to paint a picture of the system’s structure defining the core design features that provide the necessary elements which in turn provide all that follow. The model helps also in the future planning of a system upgrade. The information will also help in the implementation of the system once fully developed. Generally, the design creates an overview understanding of the system. 1.5.2 The architectural design I have chosen to use the hibernation architecture which creates a layer right between the Application and the Database. Figure 7: Architectural Design 1.5.3 Design notes The system is self explanatory and no hard jargons are used. The design is easy to understand, and the user can move from one of the system to another easily without needing assistance. The design end of the system has options that can be used to carry out maintenance which aren’t available in the web side of the system. The system has a crash dump sector which if the system happens to crash will record the current activities that led to the crash and also store the default of the system thereby allowing for a reboot and restoration of the system, though any information being keyed in or processes taking place during the crash time will have to be done again. References Khaled Elleithy (ed.)(2010). Advanced Techniques in Computing Sciences and Software Engineering.DOI 10.1007/978-90-481-3660-5, Springer Dordrecht Heidelberg London New York Java Persistence API (JPA): Java Persistence API (JPA): Mapping Sang Shin Sang Shin Java Technology Evangelist Java Technology Evangelist Sun Microsystems, Inc. Sun Microsystems, Inc. javapassion.com javapassion.com Ambler, S. 2006. Mapping Objects to Relational Databases: O/R Mapping in Detail. Available at www.agiledata.org/essays/mappingObjects.html. (Accessed September 19,2009). Bauer, C., and G. King. 2006. Java Persistence with Hibernate. Greenwich, CT: Manning. Read More