Software Engineering Report: System Design and Implementation

This report provides a comprehensive analysis of software engineering principles, focusing on the development of a customer relationship management (CRM) system. It begins with an architectural model, specifically a system context diagram, to enhance customer management efficiency and digitize feedback. The report then explores design patterns, identifying optimal solutions for common software problems, and includes a detailed class diagram to illustrate the relationships between classes such as Customer, Customer Feedback, Salesman, Product, Transaction, and Offering. The challenges of integrating sales, marketing, and customer support are addressed, emphasizing the importance of organized interaction tracking. The report concludes by evaluating the consequences of the design choices and their impact on the return on investment, with a focus on achieving a competitive advantage. The document also includes a bibliography of relevant sources.

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student
Name of the University
Author’s Note

1
SOFTWARE ENGINEERING
(A) Architectural model:
System context
The model is created for increasing the efficiency of the customer management and
digitize the feedback form for handling more data of the customer at a time. It is used for the
identification of the boundaries between the system and it demonstrated the entities that are
interacting with the system. The system context diagram is quite similar with the block diagram
and used identification of the external flows between the system and the external entities.
The system context documents how the entire system interacts with external entities
(systems and end users). It also defines the information and control flows between the system
and the external entities.

2
SOFTWARE ENGINEERING
Architecture overview
The architecture diagram is used for demonstration of the interoperation between the
systems at a high level. It is important for the development of the baseline interaction between
the actors and the systems. There are different alternatives of the system context diagram and the
architecture interconnect diagram is the best alternative found. A business model canvas can be
used for the for the development of the existing business model and its firm proposition,
customers, finances and the infrastructure are user for aligning the activities for illustrating the
potential trade-offs.

3
SOFTWARE ENGINEERING
Functional architecture
For the implementation of the functional architecture the customer relationship
management should be combined of the new business logic i.e. the application that is used for
the representation of the main business practices for example market planning and data mining.
The results can be propagated into the functional system for the execution for example upgrade
of the call center services and the completion of the sales campaign.

4
SOFTWARE ENGINEERING
Operational architecture
There are different types of applications that can be applied for the operation customer
relationship management. It can be used for fault tolerance, improvement of the performance and
the scalability of the solution.

5
SOFTWARE ENGINEERING
(B) Design patterns:
Pattern name and classification
The patters are the optimal solution for the common problems and mixing the common
problem with the community it should be resolved immediately. The design patterns can be
reused multiple times and it is important because it can act important for the design vocabulary.
A descriptive and unique name is used that is useful for the identification and referral of the
pattern.
An intent is used for the description of the goals that are behind the pattern and it is applied in
the situation where it can be used. A graphical representation such as a class diagram or
interaction diagram is used for the classification of the pattern. The participants are the objects
and the classes and their roles and responsibility should be identified for the creation of the
design.
Name and type of pattern.
The name and the type of the pattern should be identified for clarification of the
requirement of the project and develop the information system according to the needs of the
organization. The errors in the process should be processed for successful design and it should
also support reuse at the high level. The object oriented design pattern is used for demonstration
of the relationship between the class and the objects and interaction between them.
Problem
The main problem for the development of the customer relationship management system
is the collaboration of the sales, marketing, customer support and the technical support. Tracking

6
SOFTWARE ENGINEERING
should be done for interaction using an organized and systematic fashion for translating the
business into long term success. The creation of the class diagram helps in identification of the
object that are related with the other class
Solution
Customer Class – It is used for the management of the operation of the customers
Customer Feedback Class – It is used for the management of the customer feedback
operations
Salesman Class – The operation of the salesman are managed from this class.
Product class – the operation of the product are managed from the class
Transaction class – It is used for the management of the transactions.
Offering class – All the offerings provided by the business are managed in the class.
Consequences
The operators for the website cannot obtain responsibility for any consequences for the
errors or the omissions. For getting more detailed information the class objects should be
rechecked and business methods should be evaluated for the development of the customer
relationship management system.
The return of investment of the is an important factor for the management and creation of
the operation philosophy that can act as a tool for getting competitive advantage and gain a
profitable of the organization.

7
SOFTWARE ENGINEERING
Bibliography
Dart, E., Rotman, L., Tierney, B., Hester, M. and Zurawski, J., 2014. The science dmz: A
network design pattern for data-intensive science. Scientific Programming, 22(2), pp.173-185.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John Wiley & Sons.
Ghareb, M. and Allen, G., 2015. Improving the Design and Implementation of Software Systems
uses Aspect Oriented Programming.
Huo, D., Nabrzyski, J. and Vardeman II, C.F., 2015. An Ontology Design Pattern towards
Preservation of Computational Experiments. In LISC@ ISWC (pp. 15-18).
Mislevy, R.J., Haertel, G., Riconscente, M., Rutstein, D.W. and Ziker, C., 2017. Evidence-
centered assessment design. In Assessing Model-Based Reasoning using Evidence-Centered
Design (pp. 19-24). Springer, Cham.
Neil, T., 2014. Mobile design pattern gallery: UI patterns for smartphone apps. " O'Reilly Media,
Inc.".