Sale Force Automation System SFAS

1
Sale Force Automation System (SFAS)

• Software Requirements Specification

2
Group Member (B2)

• Kevin, Lok Ka Wing
• Henry, Chan Chun Tao
• Marco, Chan Wing Kin
• Harry, Lee Wai Yip
• Tse Yee Man

3
Content

• Introduction
• Scope
• Specific Requirements
• External Interface Requirements
• Specific Requirements - Software Product Features
  
• Specific Requirements - Design Constraints
• Specific Requirements - Software System
  Attributes
• Conclusion

introduction
Scope
External Interface
Soft. Prod. Feature
Design Constraint
Soft. Sys. Attributes
conclusion
4
Introduction

• Presented by Yee Man

content
5
Introduction

• staffs workload becomes much more heavier than
  before
• using traditional manual method is difficult to
  handle their job
• To ensure staffs can work properly, a new
  computerized system is necessary for the
  operations of the company in the future.

content
6
Introduction

• In our system, we mainly focus on improving the
  quality and efficiency of the work from original
  manual system with affordable cost.

content
7
Introduction (Expectation of new system)

• it can replace many manual operations and also
  paperwork to minimize the chance of making
  mistakes. Also with the improvement of working
  environment, staff morale can be improved
• customers can gain a better satisfaction from a
  better service, which can improve the image of
  the company in the market.

content
8
Scope

• Presented by Yee Man

content
9
Scope

• (SFAS) is a system that automates the sales
  activities in the company.
• It provides a set of tools for sales, supervisors
  and administrators to manage their events,
  opportunities and customers.

content
10
Scope

• It provides information to customer service
  department for performing their post-sales
  activity, based on the customers history.
• Reports will be provided for management for easy
  monitoring.

content
11
System are Divided in 5 subsystems

• Personal Information Manager
• Opportunities Explorer
• Customer Explorer
• Report
• Administration

content
12
Specific Requirements - External Interface
Requirements

• Presented by Kevin

content
13
3.1 External Interface Requirements - User
Interfaces

• Creative design for the effective delivery of
  e-services over the Internet and other
  interactive media, with dedicated attention for
  usability research, high level of manageability
  and successful branding.

content
14
3.1 External Interface Requirements - Hardware
Interfaces

• Router Cisco 1720 VPN Access Router.
• Firewall SonicWall XPRS2 w/DMZ Port.
• Switch 3com SuperStack II switch 3000 10/100.
• HUB 3com Desktop Switch 10/100 MBps HUB.
• Server3 sets of IBM E-Server X200 Server.
• Workstationfive sets of HP Brio 410 Workstation.

Diagram
content
15
3.1 External Interface Requirements - Hardware
Interfaces
content
16
3.1 External Interface Requirements - Hardware
Interfaces

• Benefits
• Protection Against Viruses from All Sources
• Increase productivity and efficiency.
• Share information and resources through a LAN and
  office automation.
• Maximize business opportunities by providing
  direct access to the Internet.
• The n-tier approaches can help rapidly and
  feasibly extend the power of IT application.

Diagram
content
17
3.1 External Interface Requirements - Software
Interfaces

• Web server Apache Web Server (ver.1.3.22).
• Application Server Jboss (ver.2.4.3) and Tomcat
  (ver.3.2.3).
• Database Server Sybase Adaptive Server
  Enterprise (ver.12.5).

content
18
3.1 External Interface Requirements - Software
Interfaces

• Benefits
• Free for use.
• A secure and stable server Application.
• Portability to all platform.
• Easy to manage and customize.
• Good for commerce purpose.
• No programming knowledge is required.

content
19
Specific Requirements - Software Product
Features (i)

• Presented by Harry (Ah Wai)

content
20
3.2 Software Product Features - Process Personal
Information Manager (PIM)

• Services
• Events Manager
• It provides daily, weekly and monthly view of the
  users schedule.
• User/Supervisor can set the default page as
  daily, Weekly and Monthly.
• User/Supervisor can add events to his schedule.

content
21
3.2 Software Product Features - Process Personal
Information Manager (PIM)

• Services
• Events Manager
• Supervisor can add the event to the staff he
  supervises.
• Details will be shown when the event on the
  schedule is clicked.

content
22
3.2 Software Product Features - Process Personal
Information Manager (PIM)

• Services
• Events Manager
• User/Supervisor can edit/delete events they
  added, But one cannot delete or edit/delete the
  event added by ones supervisor.
• Daily view shows links of different time slot.

content
23
3.2 Software Product Features - Process Personal
Information Manager (PIM)

• Services
• Events Manager
• Each time slot represents half an hour.
• Time slot with events should be highlighted.
• Weekly view shows all seven days schedules.
• Monthly view should a calendar, with event
  subjects in the calendar day boxes.

content
24
3.2 Software Product Features - Process Personal
Information Manager (PIM)

• Services
• Events Manager
• A link to meeting report will be provided after
  the event happened if a client is selected.
• A link to project progress will be provided after
  the event happened if a project is selected.
• The link to recent five events will be provided
  at the menu (LHS) which like a shortcut for users
  to access the event directly.

content
25
3.2 Software Product Features - Process Personal
Information Manager (PIM)

• Services
• Events Activate Manager
• Alert function should be provided.
• User can define how much earlier the event will
  be alerted. Alerts will be sent by email.
• A daily time schedule should be delivered at the
  time ones define everyday.
• A weekly time schedule should be delivered at
  weekday.

content
26
3.2 Software Product Features - Process
Opportunities Explorer

• Services
• Opportunities Manager
• User/Supervisor select opportunities Explorer
  from Menu at the L.H.S.
• A default page lists all the unfinished
  opportunities.
• A search box provided to search the opportunities
  by keyword and by date period.
• User/supervisor select the opportunity and the
  System shows all the notes, short conversations,
  calls, action to be taken, etc. of the
  opportunity.

content
27
3.2 Software Product Features - Process
Opportunities Explorer

• Services
• Opportunities Manager
• User/Supervisor add new notes, short
  conversations, calls, action to be taken, etc.
• User/Supervisor update the status of the
  opportunities.
• User/Supervisor add new opportunity.
• System sends email to supervisor after a new
  opportunity is added.
• The link to recent five opportunities will be
  provided at the menu (LHS), which like a shortcut
  for users to access the opportunity directly.

content
28
Specific Requirements - Software Product
Features (ii)

• Presented by Henry (Ah Tao)

content
29
3.2 Software Product Features - Process Customer
Explorer

• Services
• Customers Manager
• User/Supervisor select customer Explorer from
  Menu at the L.H.S. .
• The default page show a drop down provided to
  search the customer one want to see.
• Link should be provided to search the customers
  by the first alphabet.

content
30
3.2 Software Product Features - Process Customer
Explorer

• Services
• Customers Manager
• User/Supervisor can add Notes, Meeting
  Report, Call Record, Visit Report and
  Comment to the selected customer. (Report
  format will be further confirmed)
• User/Supervisor can add Customers.
• The link to the five most active customers will
  be provided at the menu (LHS).

content
31
3.2 Software Product Features - Process Report
Explorer

• It needs to be confirmed with the clients on the
  further meeting.

content
32
3.2 Software Product Features - Process
Administration Explorer

• Services
• A tree diagram should be provided for the
  administrator.
• Administrator can search the user by the login.
• Administrator can update/change the users
  profile.
• Administrator can change the users password but
  an email should be sent to inform the user with
  the new password.

content
33
3.2 Software Product Features - Process
Administration Explorer

• Services
• Administrator can decide ones access right
  individually.
• Administrator can add Group and its access right.
  
• Administrator can create a User and its access
  right.
• System sends e-mail to inform the user.

content
34
Specific Requirements - Design Constraints

• Presented by Henry (Ah Tao)

content
35
3.3 Design Constraints

• There is no extra server for parallel operation
  of the system. If any of the servers is down, the
  system will fail.
• If user or supervisor has forgot the password,
  they must seek help from administrator, as there
  is no field for password hints.

content
36
3.3 Design Constraints

• Use standard SQL statement instead of specific
  SQL statements in order to enhance the
  independent of the system.
• Only administrator have the control right to add,
  delete, change the database and also the access
  right of any user.
• It is essential for JSP to target the Java
  virtual machine and implement a compatible Java
  virtual machine.

content
37
Specific Requirements - Software System
Attributes

• Presented by Marco

content
38
3.4 Software System Attributes - Reliability

• Every layout has a title to classify the function
  of the page
• Every layout has similar style
• Hyperlink is in different color from normal text
• Confirmation is needed from user for any
  operation of the system
• Input data is checked and validated before
  updating the database

content
39
3.4 Software System Attributes - Availability

• Log file will be kept during the operation of the
  system for any recovery
• Backup of database will be done daily

content
40
3.4 Software System Attributes - Security

• Login and password is needed to logon the system
• User, supervisor and administrator is assigned
  different identity to the system which have
  different access right to the database
• Log file will be kept for any actions to the
  database

content
41
3.4 Software System Attributes - Maintainability

• Document for describing the system structure is
  provided
• Comment is added during implementation
• J2EE standard is used during implementation for
  maintaining the consistency of coding style

content
42
3.4 Software System Attributes - Portability

• Implementation is platform independent
• Implementation is RDBMS independent

content
43
Appendices

• Presented by Marco

content
44
Appendices

• Reference books
• Software Engineering-IAN SOMMERVILLE
  Addison-Wesley
• Software Project Survival Guide Steve McConnell
  Microsoft Press, 1988
• Business Modeling with UML Business Patterns at
  Work Hans Erik ErikssonMagnus Penker
• Object Constraint Language Precise Modeling
  with UML Jos Warmer

content
45
Appendices

• Reference books
• UML Reference Manual James Rumbaugh
• Beginning Java 2 JDK 1.3 Version Ivor Horton
• An Introduction to Object Oriented Programming
  with Java C.Thomas Wu
• Professional JSP Wrox Press Inc., StaffRobert
  Burdick

content
46
Appendices

• Reference homepages
• http//www.javasoft.com
• http//www.joss.org
• http//www.sybase.com
• http//www.hkt.com
• http//www.apache.org
• http//www.njk.co.jp

content
47
Conclusion

• Presented by Kevin

content
48
Conclusion

• The system is divided into 5 subsystems
• Personal Information Manager
• Opportunities Explorer
• Customer Explorer
• Report
• Administration

content
49
Conclusion

• Personal Information Manager
• A Microsoft Outlook like scheduler. Users can
  manage their own timetable. Supervisor can
  assigns jobs to their supervised staffs. It also
  supports group activity.

content
50
Conclusion

• Opportunities Explorer
• Tools similar to a task list. Users can create
  new projects and they can keep appending notes
  and meeting updates under the project.

content
51
Conclusion

• Customer Explorer
• Tools to keep customers record. Users can add
  notes and different reports, e.g. site visit
  report, call record, etc, to the customer
  history. Meeting reports will also be accessible
  from this module.

content
52
Conclusion

• Report
• For producing a list of reports for management
  person to do financial analysis and other CRM
  researches.

content
53
Conclusion

• Administration
• For controlling user account and access right.

content
54
End of the Presentation

• Thank you for you attention !

content