Archive for July, 2011
Step 6: Maintenance of your Asset Management System
0Once the system has been implemented it will be necessary to monitor the performance of the system over a certain period of time to ensure that it is behaving as expected. The system will also have to be maintained, and parts of it will need to be upgraded from time to time to handle evolving user needs or to cope with new requirements.
Sample Tasks:
- Logs
- Maintenance tickets
The IT group will keep an eye on the interface performance and the users will give them feedback on how it works on a day to day basis.
Step 5: Implementation
0This stage involves the packaging together of all the relevant documentation in a suitable format for distribution. In ensures everything is successfully deployed and rolled out to the users. Any change in management and/or training activities should be planned around this step.
Sample Tasks:
- Cutover Checklist
- User Guide
- Deployment Diagrams
- Training Materials
- Communications Plan
- Change in Management Plan
Now, all users (or stakeholders) can begin to enjoy the new system and take advantage of the nicely organized database. Any required training can be completed as this time or any useful documentation can be distributed to the users.
Step 4: Testing the System
0The testing stage is concerned with validation and verification of the system. The aim of the software testing is to find any errors (Bugs) in the system and eliminate them. Testing ensures that the software will perform as expected by the end user.
Sample tasks:
- Testing Senarios
- Testing Scripts
- Test Results
- User Acceptance Testing Certificate
Testers will try to break everything in the interface to make sure all senarios are accounted for. If any deficiencies are found we can back track and make the needed changes.
Step 3: System Development
0This stage is where the design is translated into a system. You want to keep a balance between quality, time, flexibility, reusability, future addition of features and/or functionality, etc…
Sample Tasks:
- Code
- State Diagrams
This step is typically executed by the technical group.
Step 2: Designing the system
0In this stage, a solution to the problem is designed by defining a logical sequence of steps that will achieve each of the previously identified requirements. The user interface will also be designed during this stage. It should be determined how input is obtained, how output is displayed, and what controls are available to the user.
Sample Tasks:
- Design Document
- Screen Mockups
- Object Model
- Sequence Diagrams
This needs to be designed in a way that makes the data easily available to the property users and displays in the correct format.
Step 1: Requirements Analysis
1During this stage of your property system project the problem is defined clearly to understand what can be gained by a property management system and what it does. After the requirements are identified a thorough analysis of those requirements should be completed. Requirements should be as detailed as possible.
Sample tasks:
- Requirements Document
- Requirements Matrix
- Use Cases
- System communication diagrams
Questions:
- Where are the contracts/projects coming from?
- how will they be used in the property systems?
- Will the property users benefit from including the new data in any existing or new reports?
Software Development Life Cycle
0this is a conceptual model used in project management that describes the stages involved in an information system development project from the initial analysis through the stabilized maintenance of the completed development.
- Requirements and Analysis
- Design
- Developement
- Testing
- Implementation
- Maintenance
How to plan for property system project
0Getting Started:
- Identifying Scope, what do you want included in the project?
- Identifying Key Players, stakeholders in this project will be everyone who is effected by what you are doing with it. Hold a meeting and ask the opinions of the stakeholders.
- Coming up with a Plan, this will eliminate mistakes and help with organization and meeting deadlines.

