The project information can be stored and shared in real time using the tools of project management throughout the organization.
Before the beginning of software process, documentation of the software project must begin. This documentation must cover the all the software development life cycle phases and the completion of the software development phase as well. The documents are generated by the documentation tools for both technical and end users.
The in-house professionals in the development team who refer the manual maintained for the system, manual maintained for reference, manual for training, manuals for installation etc.
The functioning of the system and how system works is described in the end user documents. Requirements gathering, inconsistency checks, diagrams inaccuracy, redundancies in the data etc. Example: For requirement analysis are Accept , Accompa, casecomplete etc. Total analysis can be done using visible analyst. The block structure of the software can be designed by the software designers using design tools which are again broken down into smaller modules using techniques of refinement.
The detailing of every module and the interconnections between the modules can be done using this. Whenever one version of software instance is released, configuration management tools deals with the following:. Automatic tracking, management of version, and management of release can be done with the help of configuration management.
Change Control are a part of configuration management. The changes that occur in the software after fixing its baseline or after the first release of the software are dealt by change control tools. Tracking the changes, management of files, management of codes etc. The change policy of the organization can be enforced by using change control. The programming environments like integrated development environment , library consisting of in built modules, simulation are all included in programming tools.
Testing, Supervisory or other management tasks and Maintenance. CASE tools play an important role in helping the system developers to perform the task efficiently. The whole system is composed of many active objects. Active objects AO are categorized into several groups. Active objects in the same group are responsible for the same type of tasks. This is what we call horizontal division. All AO-groups are organized hierarchically. For example, the group on top level is for users; the group on second level is for domains; the group on third level is for development knowledge; the group on fourth level is for tools; the group on fifth level is for technique support.
This is what we call the vertical division. For each group, there is a delegate which is a local server of that group. The communication among different groups is through delegates at the corresponding levels.
The system maintains multiple layers of knowledge and has the ability of self-learning and self-improvement. Especially, the system can do reasoning on incomplete information. Otherwise, the system cannot 'figure out' users' intentions and the interaction between a user and a tool will not be able to continue in some cases. Each node can be bound to a set of rules. Mixed knowledge representation is good for reducing the size of the network, and thus speeding up the learning process. In neural network, an output can always be derived from any input, even if the input is incomplete.
Self learning is a natural and standard process in a neural network. A diagramming tool, similar to DFD diagramming tool, might be useful for this purpose. Pipe-filter, event-trigger and message passing models are all useful means to realize the integration of CASE tools.
Basically, software project development is a team based activity. A CASE tool should be able to support this feature. For this purpose, it is necessary to model the work process, and the collaboration and coordination among team members. We hope to represent all these information through a work flow model. Currently, there are many ways to model a work flow for team based collaborative software development. However, most of them are too strict to change dynamically on the fly. The analysis phase identifies the overall system concept, and the project team, users, and system sponsors, then categorize the requirement into a series of version.
The most important and fundamental requirements are bundled into the first version of the system. The analysis phase then leads into design and implementation, but only with a set of requirements identifies for version 1. Once version 1 is implemented, work begins won version 2 and follows the steps, and so on. In the same way, any additional requirements identified during testing of the older version are implemented in the next version.
With this way the system gets in the hands of the users very quickly. Prototyping: The prototyping methodology performs the analysis, design, and implementation phases concurrently, and all three phases are performed repeatedly in a cycle until the system is completed.
In this case, the users of the system are an active participant of the system development process. The prototype is handed to the users for testing and to provide comments; which are the reanalyzed and redesigned, and a second prototype is developed. Two of the criticisms which have been made against RAD techniques. The facilities one would expect to find in different CASE tools ranging from the simplest to the more comprehensive toolset.
The JAD approach leads to shorter development lifecycles and greater client satisfaction because it draws users and information systems analysts together to jointly design systems in facilitated group sessions. JAD can also be adapted to developing business processes that do not involve computer automation.
JAD approach is about making effective use of your valuable time. It reduces the number of interviews needed to gather the requirements and reduces discrepancies. Everyone is in the room. JAD is a technique particularly applicable to the requirements gathering stage of the life cycle. It usually involves a series of intensive workshops between the users and the developers. The members present at JAD workshop and their roles.
0コメント