Systems Development Life Cycle

Categories: Natural Disasters

The full form of (SDLC) is Systems Development Life Cycle. It is a part of software and system engineering and information systems .It is a information system that transforms the methods and designs the models hence it consists of various software development models in software engineering.The framework for organizing and direction information system development are the strategirs formed by SLDC software development.
To automatically identify different type of offensive contents , researches have been taking place for many years.A offensive speech can fall under various categories as they can be related to religion ,nationality ,gender ,sex etc .

These type of public tweets are usually spread in the time of disaster or emergencies and involve in the plight of many people making them vulnerable .As these public offensive tweets spread across the population of a nation ,it leads to big disorganized system and law breaking scenario .This can be seen mostly in the india , where such chaos can take place even in natural disasters like flood and landslide.

These kind if information helps to create hatred and misunderstanding among many people, which turns into aggressive social harmony. These kind of situations are painful and tough for the government to handle hence leads to destruction and mobs get out of control.
the determined thinking of the population is adversely affected by disaster or the natural calamity hit on the nation. As there is misinformation all over the nation population these situations are taken as an advantage by those people who want to create offensive thinking on a particular group of a people so bad speech is spread by social media like twitter.

Top Writers
Prof Evander
Verified writer
4.8 (654)
Professor Harris
Verified writer
4.9 (457)
Prof. Clara
Verified writer
5 (345)
hire verified writer


So our main aim is to do the analysis of the tweets that spread hatred that is the communal tweets and then finding and understanding those users who spread them in disaster situations. Analysis of the tweets will be done and hence the spread of the communal tweets will be stopped by highlighting them as communal tweets this will reduce the spread of unwanted information and the government will not to face difficult hardships in controlling the mob mentality created by these tweets.No law rules will be broken and harmony will remain in the nation among groups.
SLDC consists of 6 planning stages that results in the development of a software product . The stages consists of gathering information , analysis of information and then designing and implementing it. After the implementation testing and risk taking levels are considered making it is nice project software.

 
The requirement gathering process clusters the inputs of the grant level project for the execution of the project .The inputs are gathered into different categories as per the requirements. Various major functions of different types and data entities are used in the gathering data process. So the function , data and the entities by them is used in making function and they are labeled as requirement .The demands of the requirement gathering have text illustration with identifier value.
In the analysis stage , the broad glimpse of the product software ,like the elemental framework of the project ,the risk involved with the project management and path of approach of technical terms the project.
the product requirements for the project plan (also called as goals) are extended from the requirement stage. These goals have least information of only textual description, although they can have additional information of references which can be advised as external document .The output of the project planning stage are the following reference.

  1. Management plan;
  2. Quality plan;
  3. The project plan and schedule.

The scheduled activities will be precise so that they can be used efficiently for the next requirement stages.
For sufficient and approved record , the design stage takes initial inputs as requirements.By the result of interview consultation, workshops, and prototype efforts more than one design element will be produced and this is done for each requirement. Desired or accepted software features are described by the design software , and generally include functional hierarchy diagrams, business rules tables defines the row of each business table which consists of rules which are tested on the set . It is initialized using row and column initialization.
business process diagrams- it shows all the process of business software step by step using diagram figures.
pseudo code- it shows the structure of a normal programming language.
complete entity-relationship diagram with a full data dictionary.
Each artifact is promoted and linked with explicit designs of the cases for testing purpose and is transferred by RTM,hence making it to reach in its last stages of creation. Functional satisfaction of the design elements ,application of the map with entry points . a test plan is made by the software and test cases are described elaborately .This is used to audit the software as well as its fidelity .\n the integration and test stage production include
integrated software – various software merge to form many functions , some of them are word processing, database management etc.
online help system –it gives assistance to a software application whether it is a operating system or dataset system.
implementation map – it works as a mentor for the the practical technique of planning strategies and implementing them.
initiation plan depicts reference data and production users,
acceptance plan is composed of the final confirmation of test cases, and an updated project plan.

UML Diagrams

UML,provides the software engineer with a method of expressing an analysis model following a modelling notation which is defined by a definitive set of syntactic,semantic and pragmatic rules. A UML system consists of five distinct perspectives explained using five different views.\n User Model View : This view explains the system from the perspective of a user
Structural Model view :
The static structures are modeled and presented in this view.
Behavioral Model View:
This model represents the behavioral aspect of the system and describes the interaction between the various elements of the user and structural view models.
Implementation Model View:
This model view explains the deeper structure of the model as in the working of structural and behavioral aspects as part of a complete system.
Environmental Model View
This model view covers the environmental aspect of the system i.e how the structural and behavioral components as a single system collaborates and make the implementation of system possible.

Class Diagram

Class diagram forms the initial founding block for object-oriented modeling which is used for conceptual modeling of the application which represents the basic structure of the application consisting its class structure and their internal elements. Therefore, it also helps in forming the detailed model that helps in generating code from the structure.
Class Diagram consists of block structures with three section where first one consists of the class name, second consists of the class attributes and the last seconds contains information of operations the class can perform.
Use Case Diagram
Use case diagrams are used to present the user and the system along with there different ways of interaction. It also represent the different specification of use cases. On the basic leve l it is simply a presentation of system’s interaction with the user.
Sequence Diagram
Sequence diagram is a diagram that represents the processes involved in working of the system along with the way they work together and in what order. This involves presenting a sequence of interaction taking place between different users along with the purpose they are interacting.
Collaboration Diagram
Collaboration diagram presents the different objects of a system by rectangular blocks and then using the pointed arrows to shows the flow of sequenced message in the specific order of their interaction by using the information gained from the class, sequence and use case diagrams.
Deployment Diagram
In UML a deployment model presents the components involved in the physical deployment of the program from creator to the client. The hardware components involved in deployment are represented as nodes and the software components are represented as artifacts.
Component Diagram
In UML, a component diagram is used to present the network of smaller components which in turn form the larger and complex system. This diagram shows the structure of the complex system in a refined and easy to understand manner by disecting and presenting a complex system as a collaboration of smaller and simpler systems.
Data Flow Diagram
Data Flow Diagrams are used to show the flow of data in forms of input and output which in turn provides a clear and easily understandable picture of the business function. It uses blocks to represent the different entities or objects involved in the business process and arrows to show the direction of the data flow along with the messages that are being interchanged during the process.
Activity Diagram
An activity diagram is a type of Behavioral Diagram that presents the control flow of the system from the first action involved in the process till the last one along with the intermediate stages involving different possible decision paths that could be taken during its interval of execution.

Cite this page

Systems Development Life Cycle. (2021, Oct 31). Retrieved from http://envrexperts.com/free-essays/essay-about-systems-development-life-cycle

Systems Development Life Cycle
Let’s chat?  We're online 24/7