Seminar assignments - bookstore website PDF

Preview

Summary

Bookstore Website...

Description

SOEN 6481 Software Systems Requirements Specification Fall 2015 Deliverable 1 (Bookstore Website) Team - B Buli Venkata Sri Kartheek Chebrolu Roshan Thomas Chittezhath Urvi Desai Ramanjit Dhillon Maryam Eftekhari Jesus Esteban Garro Matamoros Mandeep Ghuman Sai Teja Golla

These are base marks. The marks of individual members can vary.

P1 (10/15) + P2 (20/25) + P3 (35/40) + Organization and Presentation (10/15) + Miscellaneous Support for D1 (Wiki, Glossary, Other) (5/5) = 80.

1

The scope is reasonable but could still be reduced (say, by language or province or book subjects).

Table of Contents (In Microsoft Word, one can generate the ToC automatically.)

1. INTRODUCTION OF STARS ……………………………………………………………3 2. CONTEXT OF USE ………………………………………………………………………4 3. STAKEHOLDER MODEL 3.1 STAKEHOLDER IDENTIFICATION ……………………………………………..6 3.2 ROLES OF STAKEHOLDERS ………………………………………………….....7 3.3 MINDMAP OF STAKEHOLDERS ………………………………………………..9 3.4 STAKEHOLDER UML MODEL ………………………………………………….11 3.5 PRIORITY TABLE OF STAKEHOLDERS ……………………………………....12 3.6 ONION MODEL …………………………………………………………………...12 4. COLLABORATION PATTERNS ………………………………………………………14 5. TEAM MEMBER CONTRIBUTIONS …………………………………………………15 6. TOOLS USED FOR DELIVERABLE 1 ………………………………………………..15 7. REFERENCES …………………………………………………………………………..16

2

1. INTRODUCTION OF TO STARS The Type and Enterprise Type for our “* Is Us project” (referred as “Stars Is Us”); are: a) Book for a Type b) Bookstores for Enterprise Type. As specified in our project guidelines, our STARS project works on two key components: i) Shopping System (SS) ii) Inventory Control System (ICM). DESCRIPTION It is better to begin with a motivating argument as to why you chose what you chose at all, why your choice is important for an enterprise and how so. The Board of Directors involves Store owners and may also incorporate people such as investors. The Board of Directors also consists of non-technical personnel who are interested in the development of a store-merchant website (to be cited as Front End). The Board of Directors appoints a Project Manager who serves as the main point of contact between non-technical and technical stakeholders. Technical stakeholders are software developers employed in the development and maintenance of SS and ICM. Technical personnel are divided into teams, such as Software Development Team, IT Support Team etc. A Team consists of two or more people. Usually, a person employed, can participate in multiple teams. Members of the development teams may also be referred to as Internal Users. The Users, using the store website to buy books, may also be referred to as External Users.

The SS (Shopping System) of our Book Store consists of the Front End where External Users can create accounts, register addresses and save payment information and shop for books from any geography, however with Internet access. For now, we won't be shipping items outside Canada. In case, the Store is to have a physical location, it will be referred to as “Store Front”. Accepted payment methods through our SS (Shopping System) will be Credit Cards and PayPal for Internet purchases. At the Store Front, other options may be considered such as Debit Cards and Cash(*). Our SS (Shopping System) will not save credit card information to avoid legal and cyber-security complexities related to the storage of sensitive information in Canada. To process payments, our SS will use with a third-party payment gateway which will handle all Credit card

3

and Debit(*) card transactions. These third-party solutions may also be referred to as Payments(*). Casing has its usefulness, but why capitalize (*)?

Our Inventory Database (iDB) will not be accessible It is better to begin an explanation with a positive. directly by any External or Internal Users. If at all, only the System's administrator (also called Admin User) will have direct access to the iDB. Any change on the iDB is done via our ICM. The ICM provides a secure API It is better to avoid design-specifics. so that other systems (for example, our SS or even hardware-based barcode readers) can edit the contents of the iDB. Customer Service involvement of our SS is limited. Our SS will provide a way so that External Users can input a Customer Service Request (CSR) that will be forwarded via email to selected Internal Users in the Customer Support Team which will then resolve the problem directly with the user or will forward the Request to a member of the IT Support Team.

2. CONTEXT OF USE Be consistent: all three — you, person, user — are used.

Type of Factor User

Examples Age

Knowledge

Skills

Description Site sells product to persons of any age group. For children under the age of majority in their province of residence, you may use the site only with involvement of a parent or guardian. Note : The age of majority is 18 in six provinces: Alberta, Manitoba, Ontario, Prince Edward Island, Quebec, and Saskatchewan. The age of majority is 19 in four provinces and the three territories: British Columbia, New Brunswick, Newfoundland, Northwest Territories, Nova Scotia, Nunavut, and Yukon. OK. A person should know how to perform online transactions and must have basic knowledge of computer. User should have basic language skills like English/French and should be able to interact with GUI It is better to avoid design-specifics.. No computer language is

4

Capabilities

User Role

Education Registered

Unregistered Admin Use expansion.

User Task

Task-specific goals

Criticality of task

Frequency of use

Duration of use

Dependency of use

Risk of errors

User Goals

Overall use of software

User Activity

Criticality of use Sitting or Standing

required. User should be mentally stable so as to perform online payments. There is no limit on an education of user. A registered user can directly buy a book online by simply logging into his/her account. An unregistered user will initially sign-up on the site and then order the book. Admin can make the changes according to the need (book price, book editions, stock out). All the books listed on the site should be available. There must be a return policy within 7 days of purchase if in case any user is not satisfied with the book. Books ordered by the customers should be delivered within a specific period of time. All the tasks starting from the purchase to the delivery of the books should be of equal importance. The user can access the site from any Really? (!) Any? device 24*7 and as many times as possible. There is no time limit for searching and navigating the bookstore website for a user, but the time limit for payment gateway depends on the bank. The system should be hosted on the server which is capable of handling scaling traffic, secure and reliable. Login problems for registered users if they use incorrect user ID or password. Payment constraints- Invalid credit/debit card. The system should provide accurate, fast and secure services to the user for better customer satisfaction. High No constraints. 5

Spatiotemporal

Time Zone Current Time

Technical Environment

Network

Operating System

Server

Reliability Organizational Environment

Organizational Pressures Ethical Standards

Social Environment

Legal Constraints Social Network

Standard time What is that? Be specific. should be followed for the transactions. Time mentioned on the payment receipt should be identical with the local time zone. The connection should be uniform enough to get genuine feedback from the server. A strong network is mandatory to complete online payments in appropriate time. Operating system used should be advanced and user-friendly. This is general, and therefore not useful. A 24/7 server should be available in order to maintain the large inventory database and the server should be elastic and respond to the increased traffic. System reliability is indispensable to attract maximum users. (*) Running and Maintaining the bookstore must not exceed the estimated budget. System designed should be in accordance with the ethical standards. (*) Setup and usage of the system must be approved by the government. (*) The system should use social media, blogging, and email marketing to get in touch with the users. (*)

(*) are a bit general. Is there any system to which (*) would not apply?

3. STAKEHOLDER MODEL 3.1 STAKEHOLDER IDENTIFICATION When we analyze the software system, it can be noted that stakeholder plays an important role in defining them. Stakeholders can be broadly classified into positive and negative stakeholders based on the view of the relationship with a software project. Below listed is the stakeholders identified: 3.1.1. POSITIVE STAKEHOLDER

6

A positive stakeholder is a person, group or organization who will benefit the software project. Below listed are the set of positive stakeholders: 1. Board of Directors 2. Sales Team 3. Payments 4. Project Manager 5. Software Team a. Software Developer b. Software Tester 6. IT Support Team a. Database Administrator b. Network Administrator 7. Users a. Registered Users b. Unregistered Users c. Admin Users 8. Security Team 9. Financial Manager 10. Customer Support Team 11. Vendors 12. Inventory Control Team

3.1.2. NEGATIVE STAKEHOLDER A Negative stakeholder is a person, group or organization that has a negative impact on the project and looks a way to produce some obstacles to the project [1]. Below listed are the set of negative stakeholders: 1. Competitor 2. Hacker 3. Fraudster

3.2 ROLES OF STAKEHOLDERS The roles of stakeholders identified are discussed in detail below: 7

1. S01 - Board of Directors: The Board of Directors areis responsible for decision making in regards to the entire project with a sole aim of success. They appoint the Project Manager, Sales Team and also keeps an eye on the Competitors. 2. S02 - Sales Team: The Sales Team are the people who promote the bookstore with innovative ideas so as to attract the customers and increase the sales. 3. S03 - Payments: The place where Payment related concerns are handled for the bookstore, tasks like payment authorization and collaboration with Financial Manager are carried out. 4. S04 - Project Manager: The person who takes the responsibility of planning, monitoring and executing a software project. The Project Manager also keeps a check on the Software Team, IT Support Team and the Customer Support Team. 5. S05 - Software Team: The Team responsible for creating a well-organized ? software for the bookstore, documenting, testing, and bug fixing. This team includes maintainers who are involved in creating and maintaining frameworks in a software release life cycle. In general, their role is to set up the software system, figure out the requirements, design, test and maintain it. 6. S06 - IT Support Team: The team includes Database administrator and Network administrator, who collaborate with the software team to provide technical support. 7. S07 - Users: The Customers who accesses the website and purchase the books. The different kinds of users are Registered, Unregistered and the Admin user. The Registered user accesses his account to purchase whereas the unregistered user can either sign up for an account or continue to shopping as a guest. The Admin user accesses his account in order to update any information regarding the bookstore. 8. S08 - Security Team: The Security team keeps a check on the bookstore in order to avoid any disturbances from the Negative Stakeholders. 9. S09 - Financial Manager: The Financial Manager takes care of the finances of the bookstore and also collaborates with the Vendor for the appropriate management of Capital. 10. S10 - Customer Support Team: They provide courteous and responsive support to all customers in a professional manner and be available for users 24/7 in order to make sure that each user has an exceptional experience and ensure customer satisfaction as well. 11. S11 - Vendor: The group or an institution who supply the products, i.e books to the bookstore. The Vendors collaborate with the financial manager of the bookstore in order to maintain a particular amount of stock on a regular basis. 12. S12 - Inventory Control Team: This team performs a task like checking the stock and 8

maintaining the different kind of inventories like shipping, tracking, storage, turnover and reordering. 13. S13 - Competitor: An organization or group which challenges the bookstore for a healthy competition and influences the users in a negative way. 14. S14 - Hacker: The person who tries to exploit the website and tries to effectaffect the system in a wrong way. Not all hackers aim to do that. 15. S15 - Fraudster: A fraudster is a person with false identification, acting as real customers.

3.3 MIND MAP OF STAKEHOLDERS Mind map diagram helps in identifying the stakeholder and to illustrate the relationship between the stakeholders. Below is the initial view of mind map [3.3(a)] which was used to create a refined view of mind map [3.3(b)] for our Bookstore website.

Figure 3.3 (a) Initial View of Book Store Website’s Mind Map

9

Figure 3.3 (b) A refined view of Book Store Website’s Mind Map

It is hard to hard to identify the central concept as all the blue bubbles are of the same size. Also, this is not a mind map but a concept map.

10

3.4 STAKEHOLDER UML MODEL For object-oriented viewpoint, Stakeholder model can be represented using UML Model. In this model, a stakeholder role could be modeled as a class, and the type of relationship between stakeholders roles could be expressed using the types of relationships provides by UML [2].

Figure 3.4: UML Stakeholder Diagram for Bookstore Website

Payments is not a stakeholder. In names, use either singular or plural, but not both. Some relationship types (Affects) are general and therefore weak.

11

3.5 PRIORITY TABLE OF STAKEHOLDERS A stakeholder can be classified into different priorities such as Critical, Major and Minor based on the important for the success of a project and their influence on the progress of the project. Categorization based of priority is as follows: ● Critical: Stakeholders with high importance and influence. ● Major: Stakeholders who plays a major role in success of project but can '’t change the course of development. ● Minor: Stakeholders who are considered as needed for the success of a project but not considered to play any major role.

Below listed is the prioritization of different stakeholders in our system:

S01 S02 S03 S04 S05 S06 S07 S08 S09 S10 S11 S12 S13 S14 S15

Stakeholders Importance Influence Priority Board of Directors High High Critical Sales Team Low Low Minor Payments High Low Major Project Manager High Low Major Software Team High Low Major IT Support Team High High Critical Users High High Critical Security Team High High Critical Financial Manager High Low Major Customer Support Team Low High Major Vendors High Low Major Inventory Control Team High High Critical Competitor Low Low Minor Hacker Low High Major Fraudster Low High Major Table 3.5 Priority Table for stakeholders

3.6 ONION MODEL Why BOTH 3.4 and 3.6? What is it that one can gain from 3.6 that one does not from 3.4? This should be answered as motivation for 3.6.

12

We have used Onion model to represent positive stakeholders and negative stakeholders of the Software system. The positive stakeholders are represented in green and negative stakeholders are represented in red. The Software project P which is Bookstore website is placed at the center and collection of priorities C = {Critical, Major, and Minor} are shown as concentric circles around P. The distance of different circle from the center P is inversely proportional to and is a reflection of its degree of influence on P [2]. Collection of stakeholders identified S = {S1, S2…. S15} based on priority is placed in intervening space between circle based on priority. ● Critical: Stakeholders S01, S06, S07, S08, and S12 are placed in C1 circle. ● Major: Stakeholders S03, S04, S05, S09, S10, S11, S14, S15 are placed in a C2 circle. ● Minor: Stakeholders S02 and S13 are placed in a C3 circle.

Stakeholders: S01: Board of Director S02: Sales Team S03: Payments S04: Project Manager S05: Software Team S06: IT Support Team S07: Users S08: Security Team S09: Financial Manager S10: Customer Support Team S11: Vendors S12: Inventory Control Team S13: Competitor S14: Hacker S15: Fraudster

Figure 3.6 -– Stakeholder Onion Model for Bookstore website

13

The assignment of different colors to the rings is OK, but note that the text in the center is difficult to read because of weak background/foreground contrast.

4. COLLABORATION PATTERNS Collaboration Patterns are a form of reusable practices used by a group of people working together as a team. In our project, the below patterns have been applied in order to provide proper infrastructure for working in a group [3] [4]. 4.1 MANAGE THE PROJECT ● Define the roles and responsibilities ● Spread tasks appropriately ● Keep a check on requirements on a regular basis 4.2 ASK WHEN UNCERTAIN ● Ask Professor ● Ask TA ● Group Discussion 4.3 MANAGE WORK ● Exchange of information between group members ● Spread tasks appropriately ● Use Google Drive ● Use Wikispaces ● Use WhatsApp ● Email communication 4.4 START IMMEDIATELY Start activities as early as possible to deliver the tasks before the deadlines provided. 4.5 DELIVER HIGH QUALITY PRODUCTS Review all tasks during the project to ensure the tasks are complete and with sufficient quality.

14

5. TEAM MEMBER CONTRIBUTIONS: Team Member

Contribution

Buli Venkata Sri Kartheek Chebrolu

Worked on Problem 3 [ Research, Documentation, and Review]

Roshan Thomas Chittezhath

Worked on Problem 3 [ Research, Documentation, and Review]

Urvi Desai

Worked on Problem 1 [ Research, Documentation] and review on Problem 3

Ramanjit Dhillon

Worked on Problem 2 [ Research, Documentation] and review on Problem 1

Maryam Eftekhari

Worked on Problem 3 [ Research, Documentation, and Review]

Jesus Esteban Garro Matamoros

Worked on Problem 1 [ Research, Documentation] and review on Problem 2

Mandeep Ghuman

Worked on Problem 2 [ Research, Documentation] and review on Problem 1

Sai Teja Golla

Worked on Problem 3 [ Research, Documentation] and review on Problem 2

Wiki Hosting Service URL: https://srsteamb.wikispaces.com/space/content

6. TOOLS USED FOR DELIVERABLE 1 ● ● ● ● ● ●

Gmail Wikispaces Google Drive Whatsapp Mobile XMind 6 for MindMap Microsoft Visio 2013 for UML Model and Onion Model

15

We have used the above-mentioned tools for communication, documents sharing and producing diagrams besides them we also have followed lectures and instructions for completing the required tasks for Deliverable 1.

The references are not a numbered section. 7. REFERENCES 1. Stakeholders in Requirements Engineering. By M. Glinz, R. J. Wieringa. IEEE Software.

Volume 24. Issue 2. 2007. Pages 18-20. 2. SOEN 6481: Lecture Notes on “Understanding context” and “ Introduction to stakeholder Management “ by Professor Pankaj Kamthan. 3. http://users.encs.concordia.ca/~kamthan/courses/soen-6481/readings/Learning %20Patterns%20for%20Group%20Assignments%20-%20Part%201.pdf 4. http://users.encs.concordia.ca/~kam...