In: Computer Science
Suppose you are an analyst for the Roanoke Software
Consulting Company (RSCC), a large consulting firm with
offices around the world.
The company wants to build a
new knowledge management system that can identify and
track the expertise of individual consultants anywhere in
the world based on their education and the various
consulting projects on which they have worked
. Assume
that this is a new idea that never done before been
attempted in RSCC or elsewhere. RSCC has an
international network, but the offices in each country may
use somewhat different hardware and software. RSCC
management wants the system up and running within a
year.
The development and learning process for the developers and different offices need to be considered, as this a new knowledge management system that has not been attempted yet. A large number of users will be hesitant as well as unsure of how to the system developed. Secondly, because the offices may use some different hardware and software prototypes would need to be developed in order to gain some knowledge in a simplified version of the system to get a better understanding of what it does and how it works. After carefully analyzing the requirements of the system SRCC Company would need, I would recommend the System Prototyping methodology because this method is “quick and dirty†compared to some of the other methodologies and it would allow the different offices in each country to test out the system prototypes in the early stages of SDLC. Several prototypes can be developed and tested by the different offices in order to receive user feedback quickly in order to rebuild the prototype in the hopes of achieving maximum efficiency. Every time the prototype is rebuilt the developer would add more features in order to gain a better understanding of what individual office would need. Once the prototypes are rebuilt in a way that fits the needs of each office, they would be used to create a larger system that fits the needs of all international offices within one system.
System prototyping would allow there to be back and forth communication between the different offices and developers to quickly figure out what kind of system would fit the needs of all offices with just one system. Because the system has never been attempted by any other company, it is in the best interest of all parties involved to understand and give feedback in order to optimize the efficiency of the one system that needs to be developed.