Assignment 2 1631 Software Development Life Cycles

This assignment earns a Pass in system design. This exercise presents models in the software development process such as waterfall, scrum, agile, and spinal. Ways to draw dfd, wbs, entity relationship diagrams, mockups and wireframes.

ASSIGNMENT 02 FRONT SHEET

Qualification BTEC Level 5 HND Diploma in Computing

Unit number and title Unit 09: Software Development Life Cycle

Submission date 14/06/2023 Date Received 1st submission 15/06/2023

❒ Summative Feedback: ❒ Resubmission Feedback:

Internal Verifier’s Comments:

Signature & Date:

2.1

Table of Contents

A Introduction 7

B Task 1: Analysis (1) 7

I Identify the stakeholders, their roles and interests in the case study 7

1.1 What is stakeholder? 7

1.2 Types of stakeholders 8

1.3 Roles of Stakeholders 9

1.4 Stakeholder role with interest in Tune Source Project 9

1.5 Stakeholder requirements 11

1.6 Indentify FRs and NFRs of Tune Source Project 12

1.6.1 Function requirements 12

1.6.2 Non Function requirements 13

1.7 Discuss the relationships between the FRs and NFRs 15

II Discuss the technique(s) you would use to obtain the requirements 17

2.1 Some approach/ technique (es) suitable for the project 17

2.1.1 Joint Application Development (JAD) 17

2.1.2 Interview 19

2.1.3 Observation 21

2.2 Apply for Tune Source project 23

a JAD 25

b Interview 26

C Task 2: Analysis (2) 29

I Use case Diagram for the system 29

1.1 Use-case diagram 29

II Use case specification for 2 use cases 32

2.1 Search Songs 32

2.2 Payment song 34

III Context Diagram 36

IV Entity-Relationship Model (ERD) 40

D Task 3: Design 46

I Discuss how the user and software requirements are addressed in the design phase 46

1 Wireframe 46

a Manage Songs 46

b Register and Login 47

c Home 48

d Detail song 49

e Cart 50

f Check out 51

2 Architecture (Mock-up) 52

a Mock-up of system website 53

b Song management 55

c Register and login 55

d Home page 56

e Song detail 59

f Cart 59

g Check out 60

3 Architecture is suitable in the project 62

3.1 Server-client 62

3.2 N-tier 62

3.3 Microservice 63

3.4 Apply designs to Tune source project 64

4 Technical solution stack could be suitable to implement the project with clear explanations 68

E Conclusion 70

F References 70

Table of Figures

Figure 1: Stakeholders (Landau, 2022) 7

Figure 2: FRs and NFRs (Anon, 2023) 16

Figure 3: Admin use-case diagram 30

Figure 4: Context diagram for the whole system 37

Figure 5: Data Flow Diagram - Level 0 for the whole system 39

Figure 6: ERD of Tune Source website 41

Figure 7: Songs management wireframe 47

Figure 8: Wireframe register and login 48

Figure 9: Home wireframe 49

Figure 10: Detail song wireframe 50

Figure 11: Cart wireframe 51

Figure 12: Check out wireframe 52

Figure 13: Mokup of system website Tune Soucre 54

Figure 14: Song management 55

Figure 15: Register and login to Website 56

Figure 16: Home page TuneSource 58

Figure 17: Song detail page 59

Figure 18: Add to cart 60

Figure 19: Check out page 61

Figure 20: Client-server 62

Figure 21: N-tier 63

Figure 22: Microservices 64

Figure 23: LAMP stack 68

A Introduction

The Software Development Life Cycle (SDLC) is a systematic approach employed by organizations to develop and implement software systems of exceptional quality It offers a framework for overseeing the complete software development process, starting from initial planning and requirement gathering to the final stages of deployment and maintenance By utilizing software development lifecycle management (SDLC), projects can be carried out successfully, with clear objectives, efficient communication, and a focus on delivering value to stakeholders

Figure 1: Stakeholders (Landau, 2022)

Internal stakeholders typically include individuals or groups within the organization, such as employees, managers, shareholders, and board members They have a direct connection to the project or organization and are directly affected by its outcomes External stakeholders, on the other hand, are individuals or groups outside the organization who can be impacted by its actions

or decisions They may include customers, suppliers, government agencies, local communities, investors, and advocacy groups These stakeholders often have indirect relationships with the organization but can still significantly influence its operations and success

Stakeholders have different interests, needs, and expectations, and it is important for organizations to identify and engage with them effectively By considering stakeholder perspectives and involving them in decision-making processes, organizations can manage their interests, mitigate risks, and build positive relationships to achieve their goals Effective stakeholder management

is crucial for ensuring transparency, accountability, and long-term sustainability (Landau, 2022)

1.2 Types of stakeholders

Stakeholders can be classified into various types based on their relationship to an organization or project Here are some common types of stakeholders:

• Customers: Customers are an essential type of stakeholder for any business They purchase goods or services from the

organization and have expectations about the quality, price, and value of what they receive Satisfied customers contribute to the organization's success

• Suppliers: Suppliers provide the necessary resources, materials, or services to the organization They have an interest in

maintaining a good relationship with the organization and may be affected by its decisions or performance

• Shareholders/Investors: Shareholders or investors hold ownership stakes in the organization and have a financial

interest in its success They may include individual investors, institutional investors, or venture capitalists Shareholders often expect a return on their investment and may influence the organization's strategic decisions

• Employees: Employees are crucial stakeholders who work for the organization They have a direct interest in job

security, fair compensation, a positive work environment, and opportunities for career growth Engaging and satisfying employees is important for organizational success

• Government and Regulatory Authorities: Government agencies and regulatory bodies have an interest in ensuring

compliance with laws, regulations, and standards They may set policies, grant permits, or impose restrictions that affect the organization's operations

• Media: Media outlets and journalists can have a significant influence on public opinion and an organization's reputation

They may report on an organization's activities, conduct investigations, or shape public perception through news articles, interviews, or social media (Landau, 2022)

1.3 Roles of Stakeholders

• Manage the Leadership: Stakeholders have the opportunity to participate in the board of directors and thereby

contribute to the decision-making process They can also provide oversight for specific departments such as service, human resources, or research and development, with the aim of ensuring the organization's achievements

• They Contribute Financial Resources: Stakeholders serve as significant investors in the company, with the ability to

withdraw or inject funds as needed Their decision-making is influenced by the financial performance of the company Consequently, they may exert pressure on management for transparent financial reporting and, if necessary, recommend changes in strategies Certain stakeholders may even increase or decrease their investments to influence the market share price and create more favorable conditions for themselves

• Contribute to Decision Making: The presence of stakeholders with significant interests on the board of directors

ensures their involvement in decision-making processes alongside other board members They possess the ability to influence decisions and bring forth new ideas, sometimes exerting pressure on management to comply Moreover, stakeholders hold the authority to appoint top-level management, making their presence influential in all key decision-making areas, including judgments on acquisitions and liquidations

• Ethical Responsibility: The foremost stakeholders, being major shareholders, assume the responsibility of overseeing all

significant endeavors undertaken by the company They possess the authority to ensure the corporation's compliance with human rights and environmental regulations Moreover, they actively monitor outsourcing practices and have the ability

to vote against any business decision that compromises the company's long-term objectives

• Additional Responsibilities: In addition to the aforementioned primary roles, stakeholders undertake various ancillary

tasks within the company They possess the capability to identify new market opportunities and avenues for revenue expansion Moreover, they contribute supplementary marketing ideas and actively attract additional investors to the organization Stakeholders may also participate as members of selection committees or act as corporate representatives Furthermore, they hold the authority to make crucial decisions regarding social and environmental matters

1.4 Stakeholder role with interest in Tune Source Project

Stakeholder Roles Interest

role in overseeing and managing various aspects of a project, including its

planning, execution, monitoring, control, and closure Below is a summary of the responsibilities, qualifications, expected salary, and guidance for those seeking project manager positions

use of Tune Source services to listen to and purchase music, thereby

contributing to the company's revenue growth

John Margolis, Megan Taylor, and Phil Cooper (Entrepreneurs)

vested interest in its success They provide overall direction and strategic guidance

monitoring of the Tune Source website

Experienced with Internet technology and has worked with the ISP to maintain the existing website Responsible for implementing the necessary technical infrastructure for digital music downloads Collaborates with the marketing department to meet the business requirements

Carly Edwards (Assistant Vice President, Marketing)

implementation and ensuring its alignment with marketing objectives Provides necessary resources and support to the project team

1.5 Stakeholder requirements

aligns with the given specifications

Access to listen to music samples before making a purchase

Option to purchase individual digital music downloads at a fixed fee per download

Availability of customer subscription accounts for unlimited downloads at a monthly fee

Ability to purchase music download gift cards

User-friendly and intuitive interface for a seamless purchasing experience Reliable and secure payment processing

John Margolis, Megan Taylor, and Phil Cooper (Entrepreneurs)

Increased sales and revenue from digital music downloads

Expansion of customer base through the availability of rare and hard-to-find music

Utilization of the music archive as a valuable asset

Maintenance of Tune Source's competitiveness in the market

IT Department at Tune Source Development and implementation of a robust and scalable system for digital

Efficient search functionality and fast retrieval of music samples

Compatibility with different devices and operating systems

Carly Edwards (Assistant Vice President, Marketing)

Increased sales and revenue for Tune Source

Retention of existing customers and prevention of customer attrition

Attraction of new customers through unique music offerings

Enhanced marketing opportunities through cross-selling of complete CDs

Seamless integration of the digital music download service with existing marketing efforts

1.6 Indentify FRs and NFRs of Tune Source Project

1.6.1 Function requirements

Functional requirements refer to specific features, capabilities, and behaviors that a system, software, or product must possess to meet the desired functionality These requirements describe what the system should do or how it should perform certain tasks to fulfill the needs and expectations of users or stakeholders

Functional requirements typically outline the interactions between the system and its users, as well as the system's responses to certain inputs or actions They can include various aspects such as user interfaces, data processing, calculations, communication protocols, security measures, and integration with other systems

Functional requirements are typically documented and used as a basis for system design, development, and testing They provide a clear set of guidelines and criteria for building a system that meets the intended functionality and user

requirements (Martin, 2023)

Here's a table outlining the functional requirements of the Tune Source project, along with a description and an example for each requirement:

archive

Customers can search for music by artist, album, or genre

before making a purchase

Customers can preview a 30-second sample of each track

digital music downloads

Customers can buy and download a single song in MP3 format

for unlimited downloads

Customers can pay a monthly fee for unlimited music downloads

to log into the Tune Source system

Upon successful login, the user gains full access to all system

functionalities and has the ability to

and utilize their respective accounts to access all available services

make purchases, including buying gift cards

Tune Source's website

Seamless transition between browsing and purchasing

accounts and downloads

Customers can view their purchase history and download history

retrieval of music

Quick search results with relevant music suggestions

1.6.2 Non Function requirements

Non-functional requirements, also known as quality or supplementary requirements, specify the criteria that a system, software, or product must meet regarding its performance, usability, reliability, security, and other aspects that are not directly related to its core functionality Unlike functional requirements, which focus on what the system does, non-functional requirements focus on how the system behaves or performs (Martin, 2023)

Non-functional requirements cover a wide range of attributes and characteristics that are important for the overall quality and success of the system Some common categories of non-functional requirements include:

• Performance: Specifies the system's speed, response time, throughput, scalability, and resource usage

• Usability: Defines the system's ease of use, user interface design, intuitiveness, and accessibility for different user groups

• Reliability: Specifies the system's ability to perform consistently and reliably over time, including fault tolerance, error handling, and recovery mechanisms

• Security: Defines the system's ability to protect data, ensure confidentiality, integrity, and availability, and guard against unauthorized access or attacks

• Compatibility: Specifies the system's ability to interact and integrate with other systems, platforms, or technologies

• Maintainability: Describes the system's ease of maintenance, modifiability, and extensibility, including factors such as code readability, documentation, and architectural flexibility

• Scalability: Specifies the system's ability to handle increased loads, users, or data volumes over time without significant degradation in performance

• Availability: Defines the system's uptime requirements, reliability, and the ability to recover from failures or disruptions

Non-functional requirements are important for ensuring that the system meets the desired levels of performance, usability, security, and other quality attributes They are typically documented alongside functional requirements and provide additional guidelines and criteria for system development, testing, and evaluation (Martin, 2023)

Here's a table outlining the non-functional requirements of the Tune Source project, along with a description and an example for each requirement:

and respond quickly

Music search results should be displayed within 2 seconds

available with minimal downtime

The system should have an uptime of

at least 99%

security measures in place

Secure encryption of customer payment information

increasing user load

The system should accommodate a growing number of customers

a seamless experience

Clear navigation, intuitive search function, vivid buttons to suit the requirements of each function

users with disabilities

Compliance with WCAG 2.0 accessibility guidelines

Device Compatibility(responsive) The system should be compatible

with different browsers and devices

Support for major web browsers and mobile platforms

Data Integrity The system should ensure the

accuracy and integrity of data

Proper validation and verification of user inputs

accessible to users

The system should be available 24/7 with minimal downtime

maintain and update

Well-documented code and modular architecture

1.7 Discuss the relationships between the FRs and NFRs

The relationship between functional requirements (FRs) and non-functional requirements (NFRs) is crucial for developing a successful and well-rounded system Here are key points that highlight their relationship:

Fulfillment of User Needs: FRs focus on defining the specific functionalities and behaviors of the system to meet user needs They outline what the system should do to provide value to its users NFRs, on the other hand, ensure that the system performs these functions effectively and meets the desired qualities and attributes expected by the users

Alignment and Support: NFRs support the fulfillment of FRs by providing the necessary context and requirements for the system's performance, usability, security, and other qualities FRs and NFRs should align with each other to ensure a cohesive system design that satisfies user needs and expectations

Dependencies and Trade-offs: There are often dependencies between FRs and NFRs Changes to FRs can impact the corresponding NFRs, and vice versa For example, adding new functionalities (FR) may affect the system's performance or resource requirements (NFRs) Trade-offs may need to be made between the two to balance priorities and constraints

User Experience: NFRs play a crucial role in shaping the overall user experience While FRs define the core functionalities, NFRs related to usability, performance, and reliability directly impact how users interact with the system and their satisfaction

A system that meets functional requirements but fails to deliver on non-functional aspects may result in a poor user experience Documentation and Communication: FRs and NFRs are typically documented separately to ensure clear and focused

requirements However, they need to be communicated and understood together to provide a comprehensive view of the system's objectives, functionalities, and qualities Collaboration between stakeholders, including business analysts, developers, and

testers, is essential to ensure a shared understanding of both types of requirements

Validation and Verification: FRs are typically validated through functional testing, where specific use cases and scenarios are tested to ensure the system behaves as expected NFRs require specialized testing and evaluation techniques, such as

performance testing, security assessments, or usability evaluations, to validate if the system meets the desired qualities and attributes

In summary, the relationship between FRs and NFRs is one of interdependence and balance The functional requirements define what the system should do, while the non-functional requirements ensure the system performs those functions effectively and meets the desired qualities and attributes Considering both types of requirements together is crucial to deliver a system that meets user needs, performs reliably, and provides a satisfactory user experience (Anon, 2023)

Figure 2: FRs and NFRs (Anon, 2023)

Parameters Functional requirements Non-functional requirements

II Discuss the technique(s) you would use to obtain the requirements

2.1 Some approach/ technique (es) suitable for the project

2.1.1 Joint Application Development (JAD)

Joint Application Development (JAD) is a collaborative approach to software development and requirements gathering that involves stakeholders, end-users, and development teams working together in facilitated sessions JAD aims to streamline the requirements gathering process, improve communication, and ensure that all stakeholders have a shared understanding of the system's needs and objectives (Mrsic, 2017)

In JAD sessions, participants gather in a structured environment and engage in interactive workshops facilitated by a JAD facilitator or a business analyst These sessions typically involve the following key elements:

• Inclusive Participation: JAD sessions bring together representatives from various stakeholders, including end-users,

business analysts, developers, and subject matter experts The goal is to ensure that all relevant perspectives are considered and that decisions are made collectively

• Requirements Elicitation: JAD sessions focus on gathering and documenting requirements through facilitated

discussions, brainstorming, and interactive activities Participants share their knowledge, insights, and expectations, which helps in capturing a comprehensive set of requirements

• Collaboration and Communication: JAD promotes open communication and collaboration among participants It

provides a platform for stakeholders to express their ideas, concerns, and requirements, facilitating a shared understanding of the project goals and constraints

• Iterative Approach: JAD sessions often follow an iterative process, allowing for ongoing refinement and validation

of requirements As the sessions progress, participants review and revise the requirements based on feedback, insights, and emerging insights

• Rapid Prototyping: JAD can include the development of prototypes or mock-ups to illustrate system functionalities

These prototypes serve as visual representations of the requirements and help in validating user expectations, gathering feedback, and identifying potential issues early in the development process

• Time and Cost Efficiency: JAD can help streamline the requirements gathering process by bringing key stakeholders together in focused sessions This can lead to faster decision-making, reduced rework, and ultimately, time and cost savings

• Reduced Miscommunication and Misalignment: By providing a platform for direct communication and collaboration, JAD helps in minimizing miscommunication and ensuring that all parties involved are on the same page regarding project requirements

• Iterative Approach for Continuous Improvement: JAD sessions often follow an iterative process, allowing for ongoing refinement and validation of requirements This iterative approach helps in incorporating feedback and adapting to changing needs, leading to a more effective solution

Disadvantages of JAD:

• Time and Resource Intensive: JAD sessions require a significant investment of time and resources The collaborative nature of JAD means that participants need to dedicate time to attend sessions, which may disrupt their regular work schedules Additionally, organizing and facilitating JAD sessions can be resource-intensive, requiring skilled

facilitators and appropriate meeting arrangements (Mrsic, 2017)

• Difficulty in Managing Large Groups: JAD sessions can become challenging to manage when there are a large number of participants with diverse opinions and perspectives It can be time-consuming to ensure that every participant has an opportunity to contribute and that the sessions stay focused on the goals and objectives

• Limited Representation: While JAD aims to involve key stakeholders, it may not always be possible to include all relevant parties in the sessions Certain stakeholders or user groups may be difficult to engage due to time constraints, availability, or geographical limitations This limitation can result in incomplete or biased requirements gathering

• Potential for Dominant Personalities: In JAD sessions, individuals with dominant personalities or positional authority may have a disproportionate influence on decision-making This can lead to the suppression of alternative viewpoints

or ideas, hindering the generation of diverse and innovative solutions

• Complexity Management: JAD sessions require skilled facilitation to manage the complexity of discussions and ensure that requirements are effectively captured and documented If not properly facilitated, JAD sessions may become unproductive or result in unclear or contradictory requirements

• Scope Creep: The iterative and collaborative nature of JAD can sometimes lead to scope creep, where new ideas and requirements emerge during the sessions, extending the project's scope beyond its original boundaries Careful management and scope control are necessary to prevent project delays or budget overruns

It's important for organizations to carefully consider these advantages and disadvantages and assess whether JAD is the appropriate approach for their specific software development initiatives Mitigating strategies and proper planning can help maximize the benefits while minimizing the drawbacks of JAD

2.1.2 Interview

Interview techniques are methods used by interviewers to gather information, assess candidates, and make informed decisions during the hiring process Here are some common interview techniques:

• Behavioral Interviews: This technique focuses on past behavior as an indicator of future performance Interviewers ask candidates to provide specific examples of how they handled certain situations in the past, allowing them to assess the candidate's skills, problem-solving abilities, and fit for the role

• Situational Interviews: In situational interviews, candidates are presented with hypothetical scenarios related to the job and are asked how they would respond This technique helps evaluate their decision-making skills, critical thinking, and ability to handle challenging situations

• Competency-Based Interviews: Competency-based interviews assess a candidate's skills, knowledge, and abilities in relation to specific job-related competencies Interviewers ask questions that focus on these competencies to

determine if candidates possess the required qualifications for the role

• Technical Interviews: Technical interviews are commonly used for technical roles and assess a candidate's expertise and proficiency in specific technical areas Candidates may be asked to solve coding problems, explain technical concepts, or complete practical exercises to demonstrate their skills (Carpenter, 2022)

Advantages of Interview Techniques:

• Information Gathering: Interview techniques allow interviewers to gather detailed information about candidates that goes beyond what is presented in resumes or application forms Interviews provide an opportunity to explore

candidates' qualifications, experiences, skills, and suitability for the job

• Personal Interaction: Interviews facilitate direct interaction between the interviewer and the candidate This allows interviewers to assess candidates' communication skills, interpersonal abilities, and professionalism It also gives candidates a chance to ask questions and gain insights about the role and company

• Real-Time Assessment: Interviews provide a real-time assessment of candidates' responses, body language, and overall demeanor Interviewers can observe non-verbal cues, such as eye contact, facial expressions, and posture, which can provide valuable insights into a candidate's confidence, honesty, and engagement

• Customization: Interview techniques can be customized to match the specific requirements of the role and organization Different techniques can be employed to evaluate different competencies, such as technical skills, problem-solving abilities, leadership potential, or cultural fit

• Flexibility: Interviews can be conducted in various formats, including face-to-face, phone, or video interviews This allows for flexibility in scheduling and enables remote interviewing, making it more convenient for both candidates and interviewers

Disadvantages of Interview Techniques:

• Subjectivity: Interviews are subjective by nature and can be influenced by personal biases and perceptions of interviewers Unconscious biases may affect the evaluation process and lead to unfair decision-making It is essential for interviewers to be aware of their biases and strive for objectivity

• Limited Time and Information: Interviews typically have time constraints, limiting the depth of information that can

be gathered Candidates may not have enough time to fully showcase their skills and experiences, or interviewers may not have enough opportunities to explore all relevant aspects

• Performance Anxiety: Some candidates may experience nervousness or performance anxiety during interviews, which can hinder their ability to fully represent their qualifications and potential This can result in candidates not accurately reflecting their true capabilities

• Inconsistency: Different interviewers may apply the same interview technique differently, leading to inconsistencies

in evaluation and decision-making Lack of standardized evaluation criteria or scoring systems can affect the reliability and fairness of the process

• Limited Context: Interviews provide a snapshot of candidates' abilities and behaviors within the interview setting This may not fully reflect their performance in real work situations or their potential for growth and development

To mitigate the disadvantages, it is important for interviewers to receive proper training on conducting interviews, use standardized evaluation criteria, and be aware of unconscious biases Incorporating multiple assessment methods and involving multiple interviewers can help ensure a more holistic and objective evaluation of candidates Additionally, providing a comfortable and inclusive environment for candidates can help reduce anxiety and enhance the accuracy of the assessment

2.1.3 Observation

The observation session's main objective is to understand the actions, tasks, tools employed, and events performed by others The observation plan ensures that all stakeholders have a clear understanding of the session's purpose, agree on the desired outcomes, and have their expectations met It is important to communicate to participants that their

performance will not be assessed Throughout the session, the observer should diligently document all actions and the time taken by others to complete the activity in order to replicate it accurately After the session, the business analyst (BA) will review the findings and provide follow-up to the participants Both active and passive observation methods can

be employed (Consultores, 2021)

Advantage of Observation technique

• Real-Time Data: Observations provide researchers with real-time data by directly capturing behaviors and events as they occur This allows for a more accurate and detailed understanding of natural behavior without relying on participants' self-reports or recall

• Objective and Unbiased: Observations can offer a more objective and unbiased perspective compared to self-report methods It reduces the potential for biases or inaccuracies that may arise from participants' interpretations or memory limitations

• Rich and Contextual Data: Observations provide rich, contextual data about the physical environment, social interactions, and non-verbal cues This allows researchers to gain a comprehensive understanding of the context in which behaviors occur and identify subtle nuances that may not be captured through other methods

• Exploration of Unexpected Phenomena: Observations allow researchers to explore unexpected phenomena or behaviors that may not have been anticipated during the study design It provides the opportunity to discover new patterns, relationships, or insights that can contribute to theoretical development or further research

• Flexibility: Observation methods can be flexible and adaptable to various research settings and topics Observers can focus on specific behaviors or events of interest while remaining open to unexpected observations This flexibility allows for a broader exploration of the research area

Disadvantage of Observation technique

• Intrusiveness and Reactivity: The presence of an observer can potentially alter participants' natural behaviors, leading

to reactive behavior or participants modifying their actions consciously or unconsciously This reactivity can compromise the ecological validity of the observations

• Limited Access and Generalizability: Observations may be challenging to conduct in certain settings or with specific populations, limiting the generalizability of the findings Researchers may have limited access to certain contexts or individuals, which can restrict the scope of the observations

• Subjectivity of Interpretation: Despite efforts to be objective, interpretation of observed behaviors is subject to the observer's perspective and biases Different observers may interpret the same behavior differently, leading to potential discrepancies in data analysis and conclusions

• Time and Resource Intensive: Conducting observations can be time-consuming and resource-intensive, especially when observing complex or lengthy activities Observers need to dedicate sufficient time and effort to accurately capture and record relevant data, which can be demanding in terms of manpower and logistical coordination

• Ethical Considerations: Ethical concerns arise when conducting observations, particularly regarding privacy and informed consent Respecting participants' privacy and ensuring their informed consent is obtained can be challenging, especially in public or sensitive settings

• Observer Bias: Observers' personal characteristics, beliefs, and preconceptions can influence their interpretations and data collection process It is crucial to address observer bias through appropriate training, inter-rater reliability checks, and using multiple observers when possible

Researchers should consider these advantages and disadvantages when deciding to use observation as a research method Careful planning, clear protocols, and ethical considerations can help maximize the benefits of observation while

minimizing potential limitations

2.2 Apply for Tune Source project

Type of information

Depth of information

Breadth of information

Integration of information

User involvement

Cost

Joint Application Design (JAD)

Suitable for involving multiple stakeholders and fostering

collaboration, ownership, and consensus

gathering individual perspectives, expectations, and in-depth insights from key stakeholders and customers

Observation Suitable for

understanding existing operations, customer behaviors, and identifying areas for

improvement

Explanation of Criteria:

Type of Information: Refers to the richness and specificity of information that can be obtained through the technique

Depth of Information: Indicates the level of detail and comprehensive understanding that can be gained from the technique Breadth of Information: Refers to the coverage and range of information that can be collected using the technique

Integration of Information: Reflects the ability of the technique to gather information from multiple sources and consolidate it effectively

User Involvement: Indicates the extent to which users and stakeholders can actively participate and contribute to the requirement gathering process

Cost: Represents the relative expense or resources required to employ the technique

Based on the updated criteria, we can see that JAD and Interview is still the most suitable technique for the Tune Source project

It provides high depth, breadth, integration of information, and user involvement Interviews are also valuable, but they have a higher cost compared to JAD Observation, while useful for understanding operations, has lower depth, breadth, and integration

of information, making it less suitable for gathering comprehensive requirements in this context

a JAD

In order to gather the requirements for Tune Source project, I will use JAD:

Assist in expediting the development of IT solutions to swiftly address issues The enthusiastic involvement of customers and team members drives the continuous growth of the Tune Source project, ensuring a thorough understanding of user perspectives and requirements in order to collaboratively devise practical solutions

Taking into account the customer's aspiration to offer satisfactory services that align with their needs, the aim is to strategically anticipate and fulfill customer desires This approach enables faster and more precise documentation of system requirements compared to traditional methods By integrating contemporary technology and customer preferences into a streamlined and effective process, regular meetings will be organized involving individuals such as:

• A collaborative session will be held between the IT team and the Project Sponsor to devise the implementation strategies for the Tune Source system The primary goal is to expedite the system's launch to customers, ensuring it generates substantial revenue and maintains a competitive edge over other companies

• Moreover, conducting an interview between the ISP (Internet Service Provider) and the responsible IT team operating the current TuneSource system would be beneficial This interview aims to gather additional insights regarding the communication infrastructure currently in place at Tune Source and its operational mechanisms This understanding will enable the development of appropriate solutions for future endeavors, ensuring efficient customer service and maximizing profitability

• Arrange collaborative meetings where the client, project manager, and analysts collaborate intensively in a centralized setting, such as a single room, to establish or review system requirements and detailed designs These meetings facilitate the exchange of ideas among employees and departments, enabling system enhancements and fostering improved system development The client-project manager meeting aims to assist customers in purchasing their preferred songs, ensuring a comprehensive understanding of their needs within the Tune Source project and providing insight into future development stages Additionally, these meetings allow analysts to observe and identify areas of agreement or disagreement among users The multi-day duration of these meetings presents an opportunity to resolve disagreements or gain a deeper understanding of the underlying reasons for disagreement

The primary objective of utilizing JAD (Joint Application Development) technology is to gather system requirements from multiple customers simultaneously, creating a centralized and well-organized process that is also highly efficient This approach enables analysts to observe and pinpoint areas of consensus as well as areas of disagreement among users By conducting meetings spanning several days, there is a chance to address and resolve disagreements or, at the very least, gain insights into the underlying reasons behind the differences in perspectives

b Interview

In order to acquire the criteria for my Tune Source project, I will conduct an interview:

In order to promptly cater to customers, it is crucial to understand their requirements By conducting surveys that include targeted questions, we can gain insights into the specific expectations customers have regarding the Tune Source project This includes aspects such as interface design, payment options, and operational functionalities

✓ Prepare before interview:

Thorough preparation for an interview is vital, much like preparing for a presentation It is essential to develop a comprehensive interview plan that includes a well-structured sequence of questions, anticipates potential responses, outlines our own planned responses, and identifies smooth transitions between related topics It is important to ascertain the

interviewee's areas of expertise beforehand to avoid asking questions they may not be able to answer Additionally, we should also ensure the interviewee is well-prepared by communicating the purpose and topics of the interview in advance, allowing them sufficient time to reflect on relevant matters and adequately prepare

✓ Selection question for interview:

The selection of interview questions plays a pivotal role in ensuring a successful interview Failing to meticulously prepare pertinent questions may result in overlooking crucial information needed for a fruitful interview It is essential to identify the core information expected from interviewees and continue to develop questions that align with the project's specific business requirements

✓ Chose interviewer:

It is important to establish an interview schedule that outlines the individuals to be interviewed, the purpose of the interview, and the specific time and location of each session This schedule can be a casual list used for organizing meeting times or a formal document integrated into the overall work plan The selection of interviewees is based on the analyst's information requirements, which may include the project sponsor, key business users, and other relevant members of the project team The analyst can seek input from the project team to determine the individuals within the organization who can provide essential information regarding requirements These individuals are then listed on the interview schedule in the

recommended order of their interviews

The company's motto

1 What additional services are planned to be incorporated into the

future development of the Tune Source project?

2 Who is the target audience for the Tune Source platform?

3 What will the appearance or design of the Tune Source platform

be like?

4 What advantages or benefits will

be obtained by meeting the customer's requirements?

Available features and feature objectives

1 What is the specified deadline?

2 How many team members are involved in the project?

3 What are some existing issues or challenges?

4 Does the registration process for purchasing on Tune Source seem logical or reasonable?

5 Is there a new login method being implemented?

The standard of each song

1 From where is the extensive music database sourced?

2 Could you provide a more detailed explanation of copyright?

3 What is the process for downloading unlimited music?

Carly Edwards Project Sponor Financial allocation

Revenue generated from CD sales and online music downloads

1.What is the process by which customers can place orders?

2.What is the maximum budget allocated for the project?

3.What advantages or benefits will

be obtained by meeting the customer's requirements?

We will conduct interviews with a proficient female interviewer who possesses excellent communication skills to gather information from customers The aim is to establish a sense of trust between the company and customers, encouraging them to provide honest and candid feedback Building customer trust is crucial for the success of the interviews, as each user will have specific insights into their current system and expectations for how the new Tune Source system can serve and support their work For instance, potential customers can offer valuable information and ideas about the usage, operation, and quality of the system On the other hand, regular customers may primarily focus on the benefits the system brings, being content with their current experience rather than anticipating future enhancements All customer contributions and responses will be meticulously recorded and subsequently reviewed by the project team and implementer to assess their feasibility and compatibility for inclusion Therefore, conducting interviews with a diverse range

of customers is essential to gather comprehensive system requirements

Figure 3: Use-case diagram for the whole system

The customers registered accounts will be able to log in to their accounts, search for songs, listen to music, download tracks on demand, obtain vouchers, and purchase CDs

The system will also have a system administrator who will serve as the overall manager They will personally oversee the system's operations, including evaluating content for upload, managing client information, and handling transaction data

According to the topic requirements: By using the website or in-store kiosks, customers will be able to search and purchase digital music downloads Specific functions that the system should have include:

• Search for music in our digital music archive

• Listen to sample music

• Purchase individual downloads for a flat fee per download

• Buy music download gift card

Functions that customers are entitled to access according to the requirements:

• Login and register for a customer account

• Search, listen, subscribe and download music, buy song

• Buy or collect gift cards

In addition, the additional functions for the user are created, which are the functions of the administrator

• Admin also has some functions as client, they can listen music, download music, search music also subscribe music of website

• Manage music data warehouse such as upload song

• Manage gift cards such as issuing more gift cards to customers

• Log in and register for an admin account to access the system

In addition, I added an actor to the project, cashier They also have the following functions:

• Login and register to go to website

II Use case specification for 2 use cases

2.1 Search Songs

Use case name Search songs in Tune Source website

a particular track

• Customer can see their search products

• The customer enters a search query in the search bar

• The Customer enters the products name into the system

• The Customer choices the search button or hits enters

• The system will perform a search based on the keywords enters previously It will search the music archive for songs that match the query

• The system displays the search results, including relevant song details, to the customer

• The Customer hasn’t entered any search criteria

• If no matching songs are found:

o The system displays a message indicating that no results were found for the given query

o The system provides suggestions or prompts the customer to refine their search criteria and try again

• If the search query is invalid or empty:

o The system displays an error message informing the customer to enter a valid search term

o The system prompts the customer to enter a new search query

• The search functionality should be available to all customers, regardless of their subscription status

• The search should be performed based on the customer's query and return relevant results from the music archive

• The search results should comply with the customer's access rights and permissions For example, if a customer has restricted access to certain genres or labels, the search results should reflect those restrictions

• The search should prioritize accuracy and relevance of the results, considering factors such

as song titles, artist names, album titles, and other relevant metadata

• The system should handle different search scenarios, such as exact matches, partial matches, and fuzzy searches, to provide a comprehensive search experience for customers

• NF2: Outstanding search interface

• NF3: Only authenticated customers can access the search functionality, ensuring the privacy and security of their queries and search results

2.2 Payment song

Use case name Payment song when buying CD

purchases of CDs

Pre-condition The creation of a "Customer" account on the "Tune Source" system is a prerequisite for users

In order to make purchases, customers are required to have a bank account

Post-condition • Once the "Customer" successfully logs in, their account grants them the ability to purchase a

wide range of CDs and make payments through banking methods

• To record transaction data between the user and the payment system of "Tune Source," the company will engage the assistance of a third-party service

initially chose "Tune Source."

• Customers browse the available CDs to find the ones they wish to purchase

• The consumer assesses the quality of the CDs by considering factors such as the number of customers, reviews, and price

• Upon selecting a CD, the customer proceeds to the checkout page specifically designed for that item

• To finalize their transactions, customers are prompted to provide essential information

• The consumer chooses an online payment method from the available options provided by

"Tune Source."

• By clicking the button, the customer verifies the accuracy of the information provided and ensures that the form is complete

• To initiate the payment, the customer clicks on the designated payment button

• The bank generates and verifies a One-Time Password (OTP) for the consumer

• Following a successful transaction, the customer carefully reviews the invoice for confirmation

credentials

• Customers who do not possess a bank account or have forgotten their passwords

• The customer's bank account does not contain sufficient funds to cover the order

• The customer's chosen payment method is not accepted by Tune Source

• No response has been received from the bank's system for delivering OTP codes

• The user inputs an invalid or incorrect OTP code

• Ensuring the accuracy of the provided information prior to making a payment

• Various options for online payment, including ATM, Visa, MasterCard, JCB, ewallet, etc

• Verifying the accuracy of the bank account balance

• The time it takes for the OTP to become available

• The number of times the OTP code needs to be entered

• Completing the fields listed below: name, address, city, zip code, gender, and department relationship are mandatory

• Checking for duplicate customer information based on the specified required fields

• Newly registered users are assigned an 8-character default password

Non-Functional Requirements • NF1: It's time to seal the deal

• NF2: OTP door security

III Context Diagram