Software Engineering Project Proposal

This assignment focuses on developing a software engineering project proposal. It outlines the project scope, requirements gathering, and design considerations. Tasks include creating a database interface, coding data processing functions, generating reports, and iteratively refining the system based on feedback. The assignment also requires modeling the system using UML diagrams (class, sequence, use case), detailing use cases with scenarios and flow of activities, and addressing alternative courses of action.

System Analysis and Design for Comfort Quilts Limited
Contents
Part A.........................................................................................................................................1
Question 1: Report..................................................................................................................1
Introduction.........................................................................................................................1
Adaptive methodologies.....................................................................................................2
Recommendation................................................................................................................3
Part B: Modelling and Diagramming.........................................................................................5
Question 2: Event Table.........................................................................................................5
Question 3: Domain Model Class Diagram............................................................................5
Question 4: Design Diagram..................................................................................................5
Question 5: Use Case Diagram...............................................................................................5
Question 6: Use Case Description (intermediate)..................................................................5
References..................................................................................................................................6

System Analysis and Design for Comfort Quilts Limited
Part A
Question 1: Report
Introduction
This report outlines the process of the HCI adoption in Comfort Quilts Limited which is
currently using manual systems but wants to improve its productivity by adding IT systems to
the company. The report explores alternative methodologies and suggests most appropriate
project management methodology for development.
Adaptive methodologies
1: SCRUM
SCRUM is an Agile based software development project methodology which involves
empirical investigation and the development are carried out using adaptive feedback loops.
Project is divided into small sprints of a week or more with specific goals of development.
The methodology provides rules and procedures for iterations and meetings. SCRUM
projects involve 3 key roles including product owner, master of SCRUM and the project
team.
Advantages
 Time required for development would be less
 Cost of development would be less
 Different iterations would allow coding and testing to be done in sprints ensuring that
all requirements are sufficiently met at the end
 Feedback loop would be fast with small sprints of development
 The project progress is frequently updated which gives clear visibility
 As the project would involve conducting of daily meetings, assessing individual’s
productivity would be possible.
 A good quality software can be developed in least time spent
 With self-controlled approach, the management would not need to monitor the team
too closely
Disadvantages
 As the project would have specific finish date, any changes needed to be made in the
system would need a complete rework which can be costly for the company
 The company cannot rely on internal staff because of inexperience of SCRUM and
thus, a lot would depend on the external agency
 Tight deadlines and daily reporting can frustrate project team members
Extreme Programming
Extreme programming is also an Agile method that uses Agile principles like user
involvement, integrative development, and close coordination in teams. Development is done
in iterative cycles of one week each.

System Analysis and Design for Comfort Quilts Limited
Advantages
 Development time would be very less
 Less documentation is needed and thus, administrative work and cost would be less
 Methodology is easy to understand and codes are simple
 As everyone would work from same location, coordination is better (Pierce, 2016).
Disadvantages
 The focus would be more on coding than on the interface design
 Quality assurance procedures are not provided and thus, bugs may remain in the
software
Unified Process Development
This methodology identifies who does what, when and how. It is also incremental and
iterative methodology that uses use case development; component based architecture and
unified modelling. It considers four project aspects including product, project, process, and
people. Use cases define functionalities and sere as artefacts for development of use case
models.
Advantages
 Use cases would also capture the business value of development project
 Team can understand development processes easily as they are clearly defined
Disadvantages
 Complete requirements of comfort Quilts may not be developed
 End users are not involved directly and thus, some requirements maybe missed out
Recommendation
UP development methodology is recommended for Comfort Quilts development project for
following reasons:
 The product can be developed in less time
 Identification of use cases would make it easy to code
 Clear identification of team responsibilities would make coordination easy (Qi, 2013).
Following steps would be followed for the product development:
Step 1: Project Scope Development - 3 days
The scope of the development project includes:
 An application of suppliers must be created by sales people for approval
 Reports must be prepared on purchases and shipments
Activities that are out of scope include:
 Customer relationship management

System Analysis and Design for Comfort Quilts Limited
 Sales application
 Expenses involved in salaries and purchases
Step 2: People - 1 week
Considering the case of Comfort Quilts Limited, the three key roles would have following
responsibilities if SCRUM is adopted:
Role Responsibilities
Product Owner - Alison Williams  Define vision and priorities of development and
communicate the same to project team
 Solve queries of the team related to product
development
 Get the team involved fairly in the development
process
Project Head - Gary Tallent  Support team with expertise to achieve sprint goals
 Eliminate any issues affecting project team
performance negatively
 Advise steps to the product owner to maximize ROI
Project Team The team would have
 two programmers for coding,
 one software engineer for software management,
 one QA expert for running quality checks,
 two testers to see if requirements are met, and
 one User Experience Designer who would design the
interface
Step 3: Process Definition - 3 days
 Supplier applications would be recorded by logging into the system and capturing
necessary details including store name, business number, address, telephone, email,
country, currency goods sold in, payment terms
 Each purchase would be associated with certain shipping method and accordingly
shipping cost and time would be recorded
Step 4: Product Requirement identification - 3 days
 An inventory database storing stock levels of cotton and wool items
 A supplier database containing details of all suppliers
 An interface for purchase manager to track, approve and manage suppliers
Step 5: Prototype development in first iteration - 1 week
 Develop a computer interface to interact with the database
 Coding for data processing and report generation
Step 5: Feedback and new Iteration - 1 week
 Take feedback from team and users on missing elements

System Analysis and Design for Comfort Quilts Limited
 Make modifications in codes based on feedbacks
The development would take 30 days
Part B: Modelling and Diagramming
Event Event
Type Trigger Source Activity
System
Response
or
Output
Destination
Supplier
login
Interna
l
Procuremen
t need Supplier Data entry Data
storage
Supplier
Database
Procuremen
t reports
Interna
l
Review by
managemen
t
Procuremen
t Manager
Generate
reports
Procuremen
t report
Managemen
t user screen
Supplier
application
Interna
l Supplier bid Supplier Applicatio
n entry
Approval or
rejection
Supplier
database
update
Purchase
and
shipment
report
Interna
l
Order
processing Supplier
Run
reports for
orders,
shipments,
purchases,
and
arrivals
Query
delivering
reports
Gary tallent
and Alison
Williams as
managemen
t users
Question 3: Domain Model Class Diagram

System Analysis and Design for Comfort Quilts Limited
Question 4: Design Diagram

System Analysis and Design for Comfort Quilts Limited
Question 5: Use Case Diagram
Question 6: Use Case Description (intermediate)
Use case example:
Use Case Create a supplier
Scenario CQL wants to add a new supplier
Triggering Event New supplier has to be added in the system
Description Registered supplier can be added to allow access to the
system.
Actors Supplier
Related Use Case N/A
Stakeholders 1. Supplier
2. System
Pre-Condition NA

System Analysis and Design for Comfort Quilts Limited
Post-Condition New supplier has been added successfully
Flow of activities
Actor System
1) Supplier enters the details
3) Supplier submits details to
update customer database
5) Application is approved to
register supplier
2) The system would show a registration form with entry
fields like business name, email address, address, and
contact no.
4) System takes and forwards application to management
6) Management approves application in system
Alternate Course of Action 2.1 Incorrect data entry shows an error
4.1 Reports would be generated based on manager queries

System Analysis and Design for Comfort Quilts Limited
References
Issa. (2015). Usability and Human Computer Interaction (HCI) . Springer.
Pierce, W. (2016). Disadvantages and Advantages of Extreme Programming. Atlaz .
Qi, X. (2013). Xiaojun QiThe Software Process. Dgital CS.