logo

Different UML Diagrams in Software Development

Submit a Software Engineering assessment with a maximum word count of 3,000 words.

16 Pages3422 Words254 Views
   

Added on  2023-04-22

About This Document

This document provides an overview of the different UML diagrams used in software development, including class diagrams, activity diagrams, sequence diagrams, and use case diagrams. It explains the purpose of each diagram and their application in different phases of software development. Additionally, it compares and contrasts two UML modelling tools, Agro UML and Star UML, highlighting their features, pros, and cons.

Different UML Diagrams in Software Development

Submit a Software Engineering assessment with a maximum word count of 3,000 words.

   Added on 2023-04-22

ShareRelated Documents
Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student
Name of the University
Author’s Note
Different UML Diagrams in Software Development_1
1
SOFTWARE ENGINEERING
Answer to Question 1:
Concept of Software Engineering
The process of software engineering is applied for analysis of needs of the user and
designing, testing the end user application for satisfying the user needs using different tool
and programming languages. For the development of the software different engineering
principles are applied and complex software system are managed that can be used for
different critical business systems. The software needs of the users are taken into account for
designing the new application. It can also be used for analysing the existing software
application and modifying it aligning the application needs of the user. Since the computer
hardware are getting more cheaper focus is given on the software system for increasing the
usability of the hardware and the software system can be more complex than the hardware
and thus best practice and different software engineering process are applied for the
development of the software application. Software Engineering is applied for enabling a
discipline and control on the procedure of software development.
Concept of software development life cycle
The software development life cycle SDLC is used as a framework for defining the
task that are needed to be performed at each of the steps of software development process.
The software development lifecycle provides a structure for the development team describing
the plan that should be followed for development, maintaining and replacing specific
software. A methodology is defined by the cycle which can be followed for improvement of
quality of the software and the development process. The following are the activities that
comprises to form the SDLC model.
Planning
Implementation
Different UML Diagrams in Software Development_2
2
SOFTWARE ENGINEERING
Testing
Documentation
Deployment
Maintenance
There are different models of software development that can be followed by the
organization such as waterfall model, V-shaped model and Incremental model. Here the
incremental model is selected for involving multiple development cycles and dividing it into
smaller iterations and it is needed to be managed including design, implementation,
requirement analysis and testing.
Software implementation and its management
For the implementation of the software and management the requirement of ASDA
suppliers is analysed and the complexity in the current business process is analysed for the
management of different operation. The products are divided into different categories and
tactical level decision is taken by the senior managers for comparing the cost of the products
and provide best value weekly shop price to the customer. For the development of the
software an appropriate software development model is needed to be selected and focus is
given on the increase in return of investment and management of the workloads of the
organization. Metrics are used for quality assurance, performance, debugging and estimating
the cost and communicating different issues for the improvement of the team productivity.
The software metrics are used by the software development team for communicating the
status of software development and addressing the different issues, monitoring and improving
the workflow.
Different UML Diagrams in Software Development_3
3
SOFTWARE ENGINEERING
Answer to Question 2:
Traditional waterfall and agile methodologies
The traditional waterfall model is different from the agile model because it is a linear
approach of software development and it includes the following sequence of events such as:
Gathering and documentation of the requirement
Design
Coding and unit testing
System testing
User acceptance testing
Fixing the different issues
Delivering the final product
A distinct stage of software development is represented by each of the stages of software
development and for staring a new phase the previous stage is needed to be completed. There
are several good and bad things about the waterfall model such as:
An agreement is done between the customer and the developer about what is being
developed and this is needed for creating project plan and designing the software. A
straightforward plan and design is created with the implementation of the waterfall
model.
The progress of the development of the project can be easily measured and the scope
of the project is known to the development team prior of starting the development of
the project.
The active phases of the project can be marked and the team members should be
involved for preparing the test scripts and required documents for preparation of the
project code and starting the development of the project.
Different UML Diagrams in Software Development_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Systems Analysis and Design for Adroit Ads Company
|29
|5985
|419

Unit 9 : Software Development Life Cycle
|24
|5075
|934

Software Development Life Cycle Use In Health Care
|5
|1267
|403

Software Development Life Cycle Methodology for Online Hotel Booking Application
|30
|4922
|103

Software Engineering: Development Methods, Quality, Diagrams, and Lucid Chart
|15
|4370
|101

The Impossibility Of Requirements
|10
|2601
|31