SCHOOL OF INFORMATION TECHNOLOGY AND ENGINEERING

DIGITAL ASSIGNMENT - SWE2028

Name : Chekuru Vaishnavi

Reg No : 17MIS0088
Slot : E1 + TE1

Question : Develop two software business cases and explain the business process using
SDLC model. (Two case studies).

Case study 1 : Event Calendar to incorporate in websites

1. Problem Statement

- The calendars that are presently available are not so optimised with the
creation of events ,they cause a lot of confusion whether the events are
personnol or professional and they cannot be confidential .So here we have a
login page for each individual and colors are provided for different events to
organise. The event can be dragged,deleted, two or more events can be created
for the same date, can also be modified .All these options are available for this
calendar.

2. Software Business Cases

• Benefits

- Organize as many events as you wish

- Events are easier to find
- Distinct appearance
- Full control and flexibility
- Multiple display views
- Recurring events
• Costs

- So far no updates have been done and if needed it may cost $200.

• Disadvantages

- This calendar is not public and only those who register in the website that has
been incorporated will be using this calendar.

• Risks of current situation

- If credentials are revealed ,there would be leakage of your schedule or any

information that is inside your calendar.

• Future work

- A potential extension of this project may be the creation of a personal

calendaring system which uses the architecture of our system. This would
allow all members of the organisation to develop a personalized view of the
Events occurring in any particular organization, customized to their specific
interests and needs. The website will be futher improved to easily and feasibly
acess the site.

3. Business Process with SDLC

• Requirements

- SQL Server
- Windows
- PHP,HTTP,CSS,JAVASCRIPT
- Disk space
- RAM
- Wamp Server tool
• Design

Modules involved

i.Event Manager

- Creating events
- Editing events
- Deleting events

ii. Calendar Events

- Calendar event is the main page of the event manager and is the first
page displayed after login. Contain all of the event data for the account.
- Include event data and time.

iii. Event details

- Edit : The event details page will contain an option of editing which
displays “create event” with the data for the chosen event allowing it to
be edited.
- Remove/Delete : If the event is currently in pending list, the option to
remove the event will be available.

iv. Calendar format

- General appearance : Calendar Background , Calendar Display

- Headers : Data Header, Data Sub header.
• Implementation

- First when the user gets a page of login where if the user already has an
account else one has to register by clicking the link available.
- When the user does not account already then he comes to this page and fills
details to get registered.
- After logging in successfully, we will have options of going to other months
and also with an option of having monthly wise, weekly wise and day wise
presentation.
- When we click on the date ,it pops out a window shown below .It shows the
title ,can select color and start and end date .
- If already event is added ,the event can be edited, the color of the event can be
edited ,the title can also be edited.
- When the credemtials are wrongly provided ,it takes to a page which shows
Invalid credentials and all the details will be saved in the database.

• Testing

- Testing can be done by integrating all the modules one by one and should also
test the system with database and network connections.
Check whether corrects details are being saved in the database.

• Deployment

- The deployment of all the features are to be done and the system should rectify
all the problems.
- There should be someone to rectify if something goes wrong.
Case study 2 : AI Multi Agent Shopping System

1. Problem Statement

- An AI multiagent shopping system where system is fed with various product

details. The system allows user to register and enter his details about a
particular product. The system records all the details provided by user and
checks for various items matching his search. The system comes up with a list
of items best suited for user needs. The system also suggests other related
items that the user may like. The system suggests these items which are likely
to be bought by the user based on his previous requirements. The system
handles multiple users at a time and provides accurate results.

2. Software Business Cases

• Benefits

- The system comes up with a list of items best suited for user needs.
- The system suggests items which are likely to be bought by the user based on
his previous requirements.
- The system handles multiple users at a time and provides accurate results.

• Costs
- The upgradation might need $150 to install latest version of SQL

• Disadvantages
- If user does not specify the product details clearly ,he will get product list
which is not of his preference.

• Risks of current situation

- Since it is electronic payment , it could cause failures due to internet

connectivity.
- Might cause server issues as there will be many users using the system.

• Future work
- Can develop the android application to that system.
3. Business Process with SDLC

• Requirements

- Windows Xp , Windows 7 (ultimate ,enterprise)

- Sql 2008
- Visual studio 2010
- Processor – i3
- Hard Disk – 5 GB
- Memory – 1 GB RAM

• Design

Module involved :

- User Registration
- User login
- Multi Agent Support
- Product Categories
- Add to cart
- Custom Search
- Related products
- User Decision Considerations
- Credit card payment

• Implementation

- User can register on the system and get his online account on site.
- User can login to system and check various furniture data online.
- The multi agent guides and supports user through his entire shopping
experience and sorts out products as per user preference.
- The electronic products are arranged and can be viewed in categories.
- Users can add products to cart.
 - User may do a custom search. System take user requirements and show
products matching it.
- System also shows related products likely to bought by user.
- The agent gets products as per user preference but leaves the final decision up
to the user before making any payments.
- After total bill is calculated user can pay via credit card online.

• Testing

- Testing can be done by integrating all the modules one by one and should also
test the system with database and network connections.
- Testing if payments are done right and all the users are using the system
correctly.

• Deployment

- The deployment of all the features are to be done and the system should rectify
all the problems.
- There should be someone to rectify if something goes wrong.