Impact Factor: isra (India) = 971 isi (Dubai, uae) = 829 gif

Impact Factor: 
ISRA (India) = 4.971 
ISI (Dubai, UAE) = 0.829 
GIF (Australia) = 0.564 
JIF = 1.500 
SIS (USA) = 0.912
РИНЦ (Russia) = 0.126
ESJI (KZ) = 8.997 
SJIF (Morocco) = 5.667 
ICV (Poland) 
 = 6.630 
PIF (India) 
 = 1.940 
IBI (India) 
 = 4.260 
OAJI (USA) = 0.350 
 
 
Philadelphia, USA
389 
- incorrect organization of access and secrecy of 
information. For the successful implementation of the 
information system, it is necessary to adhere to the 
accepted standards and models for supporting the 
software life cycle. 
2. 
MODELS 
AND 
METHODS 
OF 
ORGANIZING SOFTWARE DEVELOPMENT 
PROJECT MANAGEMENT MODEL: 
The requirements analysis defines the objectives 
of the system being developed and specifies the 
requirements of future users. Figuratively speaking, 
this stage should formulate the answer to the question: 
"WHY is the system needed?" 
The specification phase defines the requirements 
of the users in terms of the functionality of the 
computer system as that functionality would appear 
from the outside. The question to be answered is 
"WHAT is a system?" 
The design phase provides an accurate model of 
the system and a detailed description of its 
implementation (“HOW to build the system?”). This 
phase is often divided into two steps: architectural 
design and detailed design, the result of which should 
be a kind of formalism, on the basis of which further 
coding of programs will be carried out. 
The implementation and development phase 
corresponds to writing programming code. 
The validation phase is the verification of the 
adequacy of the system to the specified requirements. 
It implies installation and testing of the system in real 
life situations. 
During the maintenance and support phase, 
system updates and improvements are carried out in 
accordance with the modified requirements. 
A feature of this model is the following: not a 
single step can begin until the previous step is 
completed and its compliance with the requirements is 
checked at a certain checkpoint. 
PROJECT MANAGEMENT METHODS 
RACINES (an acronym for RAtionalization des 
Choix INformatiquEs) is some action guide for project 
organizers that was first published in 1988 by the 
French Ministry of Industry. This method formalizes 
the definition and implementation of a strategic plan 
for organizing projects in accordance with the 
following five steps: 
The first step is the stage of evaluating the 
possibilities and preparing the project. Involves the 
implementation of work structures, usually organized 
around a management committee that acts as a 
decision-making body, a user group or advisory body, 
and a project team that plays the role of the main 
manufacturer. 
Assessment and orientation step - analysis of 
existing 
information 
systems 
and 
resources, 
identification of needs, priority boundaries and 
determination of the direction in which to move. 
Consideration step for possible scenarios. A 
scenario is a strategy that fills a specified set of 
objectives with a strategic plan. Each proposed 
scenario should include a conceptual solution, an 
organizational solution, a technical solution, a 
financial calculation, a sequence of actions that is 
determined by the established priorities, and an 
assessment of the potential impact on the organization 
if this scenario occurs. However, scenarios are only a 
qualitative, not quantitative, model. As a result, only 
one scenario is selected, which turns out to be optimal 
taking into account all critical conditions. 
The next step is to draw up an action plan. 
Includes the development of a progressive detailed 
quantitative description of the scenario chosen in the 
third step. At the same time, the sequence of actions 
and organizational measures is indicated along with 
the necessary technical and human resources. 
The final step is the implementation of the 
strategic plan. Typically, scenario selection takes 6 to 
18 months, while an action plan can take 5 to 10 years. 
Disadvantages of the method: 
- The method does not always identify the 
required resources or quality control processes for the 
products obtained at each step. 
- The method is not well suited for large projects, 
where the specification may change. 
Software 
development 
technologies 
are 
progressing very quickly and currently allow 
significant results to be obtained in a short time. The 
result can be obtained in the form of prototypes, which 
are provided directly to the user. 
The spiral method is based on the principle of 
incremental development. New features are added at 
each step (increment). Each turn of the spiral includes 
requirements 
analysis, 
specification, 
design, 
implementation, and validation. 
At the end of each loop, a new version of the 
software is produced, which will be operated until the 
next phase ends. 
Spiral method and rapid prototyping help 
improve the management of project resources. 
Explicit specification of system versions allows 
checking and verification of each version. While not 
guaranteeing that cascading errors (initial errors that 
multiply in the next stages) are eliminated, this 
method guarantees that they are eliminated, allowing 
you to return to the latest acceptable version of the 
system at any time. 
However, system analysis gives rise to many 
intractable problems, including: 
- Inability to obtain comprehensive information 
to assess the system requirements from the point of 
view of the customer. 
- The customer does not have sufficient 
information about the data processing problem. 
- The specification of the system is often 
incomprehensible to the customer due to the scope and 
technical terms. 

---