Effective Software Development ProcessWritten by Blane Warrene
Continued from page 1
* Does architecture meet standards of organization and industry standards? * Scale of system to handle level of use and growth of systems such as data storage, new interfaces, future improvements and modules. User Interface Design This can be a web browser based GUI or a software GUI. Either way, consideration should be given to both design of interface and discussion of how to handle changes to interface so as not to disrupt underlying application development. Database Design This is place to architect top-level view of database for this application. Depending upon scale, perhaps some ETL (extraction, transformation and load) tools may be used for design purposes. This is an area where challenges and risks can be identified further, as mentioned earlier. This would include reliance upon data sources or interfaces outside of control of technical team. Roles and Responsibilities A final step is to assign resources to varying sections of whole application. This is where expertise and experience are married to components and systems required to complete project. The completed design specifications will naturally lead to a functional specification. This makes it important to take an additional step prior to moving forward. This is a good time to bring original charter group back together with a presentation that shows how design of system answers business requirements and meets overall scope of charter. This discussion will most likely bring about some changes to design, and previously agreed upon change management process should be used to update design specification and move on to final stage prior to getting programming started. Functional Specification The goal of a functional specification is to achieve a handbook reference for technical team to develop, integrate, test and finally release a completed application. This document is much easier to complete with previous road map documents in hand. The technical team will never lose sight of business goals through charter and requirements, and design document has set parameters through which project will be accomplished. Also, repeated steps of communicating back to original group keeps flow of information on status and issues between business and technical teams and support does not waver for project. Now is time to address language specifics and how issues such as hardware and software dependencies and limitations will be addressed, performance requirements, security requirements, error handling and overall logging requirements. The applications varying sections are addressed with resource(s) in mind. This will enable a very clear timeline to be drawn and matched against original timeline from charter and updates may need to be provided to original group (keep in mind those QA and testers we mentioned) for scheduling. Again, be sure to use change management process. The completed functional specification will read like a technical reference guide for resources to construct application. It will provide a timeline to be followed and reported upon. And ultimately, it should lead to successful testing and completion of project. Conclusion Critical to success of any endeavor is communicating issues and solutions, and steps to achieve results. In application development, communication is very critical, not just between technical team members, but also between senior management and business users involved in project, as well as your QA and testers who will sign-off prior to deployment. The steps of any application project use business charter, business requirements, design and functional specification to ensure scope management and that goals are met with end result. However, there can be a disconnect between these parties as project is underway and coding begins. This can lead to loss of momentum and support from non-technical staff and managers, scope creep and/or misunderstandings, which may lead to failure. To avoid this, consider setting broad parameters for reporting status and general communications when building charter at inception of project. These can be scheduled meetings, e-mail updates and even presentations as needed. Also ensure your change management process is in charter, and that it entails communicating change requests to this group with a clearly defined process for approvals and comments. While some of project will seem technical and difficult to follow by non-technical team members, group remains informed, can feel they are invested in success of project, and can be your biggest cheerleaders when obstacles arise.
Prior to participating in the founding of BMRW & Associates, Blane served most recently as the Director of Technology for VESTAX Securities Corporation. In this capacity he was responsible for the management and evolution of the IT infrastructure and services for internal operations and field technology services for VESTAX financial advisors. Blane brings substantial knowledge in application & data integration, mining and management .
| | Information Security PolicyWritten by Blane Warrene
Continued from page 1
Back to TopA daily and monthly data backup process should exist which also provides for off-site or fireproof storage of backup data in a non-editable format (i.e. offline magnetic tape or CD-R (not CD-RW)). Any connection to Internet, from a shared 56 K modem to a broadband (DSL, Cable or T1) connection, should be behind a software or hardware-based firewall. If not, this is an immediate and gaping hole through which crackers can access your private network or use your computer for an attack on a larger public or private network (often called a DDOS or Distributed Denial of Service attack). Use a password to login to your computer even if it is not on a network. Passwords should be at least eight characters and changed as often as tolerable (90 days is a satisfactory time period). Use and update daily an anti-virus software suite, which can protect your individual computers as well as any servers you use. By taking these steps, you are dramatically reducing your exposure to uninvited intrusions. The inventory you established earlier can then be reviewed and a plan can be developed by your business and your technology staff/consultant to ensure your office network and data is a fortress with a little risk as possible. Learn More About Securing Your Computer, Data and NetworkSecurity Tracker This site tracks all known vulnerabilities and threats in Internet and network technology. http://securitytracker.com Microsoft Security Micorsoft's site dedicated to their own applications, including software patches and alerts to newly discovered security issues. http://www.microsoft.com/security/default.asp TinHat The ABCs of web and Internet Security. http://www.tinhat.com/
Prior to participating in the founding of BMRW & Associates, Blane served most recently as the Director of Technology for VESTAX Securities Corporation. In this capacity he was responsible for the management and evolution of the IT infrastructure and services for internal operations and field technology services for VESTAX financial advisors. Blane brings substantial knowledge in application & data integration, mining and management .
|
