Unit 9: Software Development Lifecycle for E-Commerce Website Report

This report provides a comprehensive analysis of the Software Development Lifecycle (SDLC) for an e-commerce website, addressing the needs of a medium-sized business seeking to replace its outdated static website with a dynamic, user-friendly platform. The report begins by outlining the project requirements, including functional and non-functional aspects, use case descriptions, and traceability considerations to ensure the developed software meets all client demands and stays within budget and time constraints. It then delves into the suitability of software behavioral design techniques, covering interaction design principles and the importance of early testing, a changeable environment, and the application of design paradigms to improve software quality. The report emphasizes the importance of early testing and adaptability to ensure high-quality software and concludes with a discussion of the key features of an e-commerce website, such as shopping carts, payment gateways, and content management systems. This report is a valuable resource for students studying web development and software engineering, offering practical insights into real-world project management and SDLC implementation. The report is available on Desklib, a platform offering AI-based study tools for students.

Running head: SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE
WEBSITE
Software Development Lifecycle for an E-Commerce Website
Name of the Student
Name of the University
Author note

1SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
Table of Contents
Introduction: 2
Discussion: 3
Task 1- Undertaking software development lifecycle: 3
Task 2: Discuss the suitability of software behavioural design techniques: 9
Conclusion: 12
References: 13

2SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
Introduction:
The aim of the report is to provide a solution to a medium-sized business that
has approached the Circle solutions for creating a new website replacing their old
static website with a new dynamic website. The company want to replace their old
website as the website is static in nature and is not up to date with all the upgrades
that were needed (Bridges and Rempel 2013). The website was unable to be
accessed in the hand driven devices like the smart phones and tablets or other new
internet accessible devices.
To mitigate the problems faced by the organization, the Circle solutions will
evaluate the Software Development Life Cycle model (SDLC) which will be used
and applied for developing the new software based solution desired by the
organization client (Mishra and Dubey 2013). For developing a software project,
the general and basic needs and criteria are fulfilled by the Software development
life cycle model. The SDLC can be stated as complete form of procedures which
helps the project of the website development lad to the way of completion and in
the success of execution. The aim of the project is to complete the application and
transform from the primitive technology. The old application or the website
domain has failed to reach the expectations of the business markets in the recent
times which have compelled the organization to transform the static website to a
dynamic website for the enhancement of their business policies and structures
(Shuaibu et al. 2015). The change in the system can prove to be more efficient in
the market. The main challenge of the Circle solution executive is to deliver the
solution within the given limited time as well as the budget.

3SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
Discussion:
Task 1- Undertaking software development lifecycle:
1. The project that has been assigned to the Circle Solutions is about developing a
website which will be dynamic in nature for the medium-sized business
infrastructure. A website page comprises of many interactive elements as well as
dynamic and static entities that are associated with the webpage. The webpage
consists of text words and multimedia applications including the image filers and
backgrounds that come under the graphical part. The basic language platform
requirement consists of HTML, XML, CCS, PHP and SQL.
The functional requirements consists of the Following of the rules of business
that is maintained and states that a website must contain the characteristics of
fundamental quality for the purpose of the business it is serving (Chen et al.
2016). The webpage must contain all the attributes that are required by the
medium sized enterprise for executing their business transactions (Wiegers and
Beatty 2013). The portal must have the ability have all the control on the
transactions on the website including the corrections and rejections of the kind of
the work that is done. The interface of the website must be present so that the
outsiders feel easy to use the system (Shostack 2014). There must be compliance
with corporate governance demands. The scheme must meet a company's legal
demands and adhere with its governing body's laws. It must be in basic,
unambiguous English to create it easy to navigate and customer-friendly. It should
be able to give its users permission. This allows users to function in almost the
same scheme as their user power in distinct levels.

4SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
The non functional requirements states that the Performance Parameters are
the non-functional requirements and this involves the system's reaction time, the
use amount from both the static and adiposity types of throughput. Recovery
involves about the system that would be able to rebound from an accident
(Leonardi and Van De Ville 2015). It is necessary for the system to recover itself.
It is necessary, in order to guarantee safe documents present in the scheme and
that unapproved staff cannot access them, and the safety measures should be
included in the structure.
2.

5SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
Use case description:
Register: If a client is a fresh user, the registration page can be requested. A
registration page opens and requests complete client data and also ask the
client to select login (email address) and password.
Login: By entering the name and password, the client can login. The system
checks matches for name and password. If not complemented, the client will
receive error messages.
3. Traceability relates mainly to the quality control of demands through most of
application growth in the software development lifecycle (SDLC) (Regan et al.
2014). This helps guarantee that the supplied software meets all demands and
therefore helps avoid errors. The factor of Traceability is a primary requirement
for effective management of software requirements.
Software always includes bugs which need to be fixed, but traceability helps
to find and correct these bugs so that failures are minimized. In general,
traceability enables to provide business-specific software on time and on budget.
Traceability requirements are a critical component in the growth of applications
(Regan et al. 2013).
Providing more requirement metrics to the Circle Solutions will help them to
define the level and parameters of the expectation of the developing team. This
will enable the more accurate implementation of the specified needs. It will
enhance the quality of the webpage that is being developed by the team and also
ensures the team that the contents are appropriate and are matching with the
company’s requirements (Regan et al. 2015). Advanced traceability demands can

6SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
improve team incentive and client satisfaction while simplifying the life cycle of
your growth.
4. Finding methods to implement efficient testing strategies at an early stage will
assist the developers in identifying and resolving flaws. The early recovery from
the issues in the phase of project management develops an advanced and
advantaged situation for the company. Improved effectiveness leads to better
software quality and lower expenses (Carreño and Winbladh 2013). On the other
hand, bad quality of software exacerbate issues and could be time consuming and
costly.
Test early and test often-
Often testing is essential for enhancing software quality. Initial testing will
ensure that no snowball deficiencies are becoming more complicated and larger
issues. The higher the place to judge, the more expensive it is to get rid of issues. As
shortly as you get involved with your testers, the better is the output received from the
developers ( Ammann and Offutt 2016). To ensure that testers remain on all issues
and errors as they happen and this is before problems evolve exponentially, it is
proposed that testers be engaged early in the software design stage. Testing often
includes early focusing on the right integrated management of the scheme. First, non-
UI tests are streamlined and afterwards the UI visibility rises slowly whenever the
product stabilizes (Kaur and Gupta 2013). For guarantying that all the rules made by
the company and the applied logics are tested, the web services or APIs are used to
evaluate.

7SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
This is also a prime moment for working together with the programmers for
guarantying that the automated testing of the webpage product is also getting
implemented in the development team.
Plan for a changeable environment-
Software has many parameters and is changing. It is based on various of
external variables, including web browsers, computers, databases, and software.
Those same stable internal factors indicate that the progress of software must be
continually monitored through checks and balances to certify its advancement in its
instant environment. Recognizing the interconnectedness of technology on these
internal factors is crucial. If the business recognizes this interconnectedness, this can
plan ahead (Obeidat and Nasereddin 2013). Testers can check the quality of the
technology against internal variables to see how it is endorsed at each point of the
process. This can prevent software dysfunction and maintain the quality of the
software.
5. Improving the software quality by the use of function design paradigm in SDLC:
During the course of development of the website software, a paradigm has the
ability to guide and show the way that is needed by the developers to get the
insight of a given problem. This also allows analyzing the problem and organizes
the desired solution for the developers. The developers follow the particular
process for developing the large website system or software system that is more
complex by breaking down the entire process of development in to simpler and
smaller phases (Ahmed and Zeeshan 2014). This helps the developing team to
manage the steps well and mitigate the problems simultaneously.

8SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
The objective of the design paradigms is based on and is derived from the
basic concept of paradigm which is based on the Sociology of science. There two
conceptual meaning of design paradigm. The software quality can be improved by
the Models and archetypes which is one of the two types of the Design paradigm
that helps in the software development life cycle (Ralph 2013). In this sense, a
paradigmatic design relates to a architecture solution that is considered a success
and prominent by a group. Achievement is usually associated with share of the
market or any other evaluation of prominence, but it might not be the case. The
aim is to create the influence in the successful layout and designs irrespective of
the fact of getting poor results from the market or being commercially down.
The sociological paradigms are the design paradigms that are group of beliefs
as well as information. This allows applying for a particular community based
design.
The paradigms improve the software quality as the Software design paradigm
in a software development life cycle represent the output which has been desired
by the people or is been derived from the ideas of the people on the process of
construction of programs (Ralph 2013). These connect them in to vast systems of
the software and formal mechanisms that help to describe the nature and the
process how the ideas will be implemented. We can therefore conclude that a
Software Design Paradigm is indeed a model for a class of difficulties that express
a number of common features.
A design pattern is a demonstrated answer to a particular design issue. It
comprises of transmitting' objects' that are tailored to solve the issue in a particular
context. Trends originate in object-oriented programming where they started as
sets of objects arranged to fix a issue. There is no basic connection between

9SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
patterns and items; it just occurs that they started there. Patterns might have arisen
even though objects seem so elementary, but the issues we tried to fix for them
were so complicated (Lee and Wong 2016).
Task 2: Discussing the suitability of software behavioural design
techniques:
1. addressing user and software requirements of an E-commerce website-
The E-commerce website developed and programmed by The Circle Solutions
attains certain attributes that are specifically usable for the E- commerce based
business website alone. The E-commerce based website attains specific features
like the feature of shopping carts, payment Gateways, order management,
security, scalable infrastructure, mobile compatibility, Mobile compatibility,
reports and communication panels, content management systems and logistics
integrations (Amálio and Glodt 2015). The website portal will have the seven key
features like the Ubiquity, the Standards maintained in an universal state, Global
Reach, Information Density, Richness, Interactivity and the characteristics of
Personalization.
2. Software behavioral specification of website:
Any piece of software, coded in some programming language,
implicitly indicates the behavior it will generate when running on a specified
computing scheme with a set of input information. Behavioral specification is
a specification of the system's dynamic behavior as it is being executed. They
demonstrate what occurs or what is expected to occur when a system reacts to
stimulation from its setting.
Example 1) Interaction design principles:

1
0
SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
This type of situation arises due to the lack of the knowledge sharing
with the interaction designer or developer or generally known as the UX
designer. This forces to face the consequences on the project. A website
developer may not have designed business applications, and so he did not have
the sufficient required experience in the features and working process of the
UX design requirements for Windows, Mac OS X, or Java. These help to
specify and set the parameters with primitive functions and characteristics of
the older system. (Ringert, Rumpe and Wortmann 2014). This problem can be
mitigated by the use of documents on UX principles and guidelines.
Example 2) Failure of developers in implementing the website as designed:
Company would spend in improved interaction design, and then
wasting their expenditure by enabling designers to disregard development
demands is inexplicable. However, this occurs all too often in engineering-
driven organizations. Strong technicians could have supersede UX designs
generally on the costing done by compromising company objectives instead of
doing what would have been best for well-being and continued life of a
company. To overcome this difficult issue involves converting importance of
experience of the user conveyed to the leaders of the company or the
organization, managing changes in the organization infrastructure, to convince
developers to embrace concepts and to educate the peers in many other areas
on outstanding architecture principles and instructions.
If a customer perceives listings for either a particular time or date, he
or she must re-launch his or her search engine; the implementation does not
retain the user's previous time and date settings throughout the sessions.

1
1
SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
Date and time issues which have the characteristics of generalized
drop-down entrees on the Fan-cast Browse Listings page which have been
characterized under the architecture principle are indeed examples of failure to
understand user configurations. Even though these screen configurations are
generally relatively straightforward to change, resetting them constantly has
become annoying.
3. Finite State Machine:
A finite state machine that is also known as the finite state automaton
is a computational model which is introduced along with the network
connectivity which can be used to visualize synchronous line of reasoning and
even the computer programs are considered. The Finite state automations
generate periodic based languages.
Extended Finite State Machine:
In such an expanded finite state machine (EFSM) model, a "if
statement" composed of collections of activate circumstances can convey the
transition.
The distinction between both the Finite State Machine and the
extended Finite State machine could be explained in terms of Boolean
conditions input sets along with the Boolean output feature set. And in an
Extended Finite State Machine Model, the transformation method differs by a
if statement that basically consists of activation circumstances. If all Trigger
requirements are met, the transformation will be discharged, working to help
take the computer from the present state towards the next state and performing
the given information operations. An EFSM includes and is described by
seven tuple elements. Whereas FSM includes five tuples of elements.

1
2
SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
4. The good thing about the use of data to drive design is that it provides the
website with more information about what works and what falls flat. In the
design process, intestinal emotions and preference can often take precedence
over rational thinking in design.
Whenever a shift is made to both the design of the internet, the
organisation does not want it to be a shot in the dark. Gathering information
when someone does something like altering a software function will inform
the developer whether all the modifications they've created are functioning
and will assist them deeper comprehend what consumers are responding to
and who they are not doing.
Conclusion:
In evaluating the requirements of e-commerce websites for medium-sized
business, the important elements of the e-commerce business strategy must be
addressed to considerably support business achievement. This can also be realized
at the important stage of the requirement analysis by developing a suitable series
of operations. After defining company possibilities that can be developed or
captured by small sized business organization, the operations are, identifying
market possibilities, business climate and benefit, after which formulating
company goals, establishing value proposition, income structure and marketing
campaign, as well as developing organisations and business processes

1
3
SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
References:
Ahmed, Z. and Zeeshan, S., 2014. Cultivating software solutions development in
the scientific academia. Recent Patents on Computer Science, 7(1), pp.54-66.
Amálio, N. and Glodt, C., 2015. A tool for visual and formal modelling of software
designs. Science of Computer Programming, 98, pp.52-79.
Ammann, P. and Offutt, J., 2016. Introduction to software testing. Cambridge
University Press. ( Ammann and Offutt 2016)
Bridges, L.M. and Rempel, H.G., 2013. That was then, this is now: Replacing the
mobile-optimized site with responsive design. Information Technology and
Libraries, 32(4), pp.8-24.
Chen, D.D., Woo, M., Brumley, D. and Egele, M., 2016, February. Towards
Automated Dynamic Analysis for Linux-based Embedded Firmware.
In NDSS (pp. 1-16).
Galvis Carreño, L.V. and Winbladh, K., 2013, May. Analysis of user comments:
an approach for software requirements evolution. In Proceedings of the 2013
International Conference on Software Engineering (pp. 582-591). IEEE Press.
Kaur, H. and Gupta, G., 2013. Comparative study of automated testing tools:
selenium, quick test professional and testcomplete. Int. Journal of Engineering
Research and Applications, 3(5), pp.1739-1743.
Lee, C.S. and Wong, K.D., 2016, July. Learning e-commerce web design
engineering: Towards discovery of service innovational opportunities. In 2016

1
4
SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
IEEE 16th International Conference on Advanced Learning Technologies
(ICALT) (pp. 404-406). IEEE.
Leonardi, N. and Van De Ville, D., 2015. On spurious and real fluctuations of
dynamic functional connectivity during rest. Neuroimage, 104, pp.430-436.
Mishra, A. and Dubey, D., 2013. A comparative study of different software
development life cycle models in different scenarios. International Journal, 1(5),
pp.64-69.
Obeidat, J.A. and Nasereddin, H.H., 2013. A new vision for information
technology project management through selecting SDLC model. American
Academic & Scholarly Research Journal, 5(4), p.183.
Ralph, P., 2013. Software Engineering Process Theory: A Multi-Method
Comparison of Sensemaking-CoevoIution-Implementation Theory and Function-
Behavior-Structure Theory. arXiv preprint arXiv:1307.1019.
Ralph, P., 2013. The two paradigms of software design. Available at SSRN
2238571.
Regan, G., Biro, M., Mc Caffery, F., Mc Daid, K. and Flood, D., 2014, June. A
traceability process assessment model for the medical device domain.
In European Conference on Software Process Improvement (pp. 206-216).
Springer, Berlin, Heidelberg.
Regan, G., Flood, D. and Mc Caffery, F., 2015, June. The Development and
Validation of a Roadmap for Traceability. In International Conference on
Software Process Improvement and Capability Determination (pp. 45-57).
Springer, Cham.

1
5
SOFTWARE DEVELOPMENT LIFECYCLE FOR AN E-COMMERCE WEBSITE
Regan, G., Mc Caffery, F., Mc Daid, K. and Flood, D., 2013. Medical device
standards' requirements for traceability during the software development lifecycle
and implementation of a traceability assessment model. Computer Standards &
Interfaces, 36(1), pp.3-9.
Ringert, J.O., Rumpe, B. and Wortmann, A., 2014. From software architecture
structure and behavior modeling to implementations of cyber-physical
systems. arXiv preprint arXiv:1408.5690.
Shostack, A., 2014. Threat modeling: Designing for security. John Wiley & Sons.
Shuaibu, B.M., Norwawi, N.M., Selamat, M.H. and Al-Alwani, A., 2015.
Systematic review of web application security development model. Artificial
Intelligence Review, 43(2), pp.259-276.
Wiegers, K. and Beatty, J., 2013. Software requirements. Pearson Education.