There are a variety of information system development tools and techniques. One very effective technique is modeling. An organization can utilize the modeling technique in mapping out and planning how to implement the software development life cycle in order to execute their software strategy.
Modeling techniques are data flow charts and activity models. As a technique, a data flow chart distinguishes and labels the entities and relationships which it deems essential in developing software. Modeling techniques also have a notation and representation structure. In a data flow chart, the notation for a process can be represented by circle, and, for a data flow, a solid line with an arrow-head can be used. The representation structure of a data flow chart is a visual chart. Additionally, a modeling technique details which sort of features of an entity software package need to be taken in, in what notation each feature is represented, and how these representations should be created (Tolvanen, 1998).
An organization can implement the modeling technique in the software development life cycle (SDLC) in executing their software strategy. This process consists of recognizing and investigating the problem, understanding the current software and the new software’s needs, planning the new software, creating the new software, converting to the new software, and continuously monitoring and adding value to the new software (Senn, 2004, p. 442). The modeling technique can be utilized throughout the whole SDLC in order to plan and stay on course.
An organization should use the SDLC along with the modeling technique in much the same way Chevron’s information technology (IT) team is introducing a new software package which supports its engineers in the field in monitoring steam migration throughout the oil reservoir. The IT team did not just throw together a package and tell the engineers to work with it. Instead, they modeled out a plan, developed a preliminary package based off of compiling features of various software into one robust package. Once this was done, the end-users were allowed to test out the software for a day or two and provide feedback on what they liked, did not like, and what features they would like to see added. The final product has yet to be rolled out as Chevron IT is still making changes in accordance with the feedback provided, but when this software package is complete, it will be very effective and very efficient.
Senn, J. (2004). Information technology: Principles, practices, and opportunities (3rd ed.). Upper Saddle River, NJ: Pearson Prentice Hall.
Tolvanen, J. (1998). Incremental method engineering with modeling tools: Theoretical principles and empirical evidence. Jyväskylä, Finland: University of Jyväskylä. Retrieved October 27, 2009, from http://users.jyu.fi/~jpt/doc/thesis/ime-2_1.html