Innovation Station
Needs analysis statement
table of Contents
-
1 Introduction
1.1 write Objective 1
1.2 Project Risk 2
1.3 2 Read the intended audience and recommendations
1.4 product range 2
1.5 References 2
overall 2 2. System Overview
2.1 Objective 2
2.2 user classes and features 3
2.3 3 runtime environment
2.3.1 Hardware environment 3
2.3.2 software environment 3
2.4 design and implement restrictions on 3
2.5 assumptions and constraints (dependent) 4
2.5.1 product SEO ranking 4
safety system 2.5.3 4
3. external interface requirements 4
3.1 4 user interface
3.2 hardware interface 4
3.3 software Interface 4
3.4 4 communication interface
4. The system features 5
4.1 Description 5
4.2 5 functional requirements
5. other non-functional requirements 6
5.1 6 performance requirements of
5.2 needs safety measures 6
5.3 7 security requirements
5.4 operational requirements 7
5.5 software quality attribute 7
5.6 business rules 7
5.7 7 user documentation -
Introduction
1.1 purpose of writing
this needs analysis statement for the contents of the first phase of the project to analyze the demand and implementation details for a more detailed elaboration. This requirements specification for business and technology sector personnel, personnel software requirements, outline design software personnel, software developers, software testers, and confirmed as the basis for product acceptance.
Needs analysis is based on the feasibility study, the users of the system described by analyzing the developer summarized, abstracted into a complete requirements definition, and then the formation of a series of documents. Feasibility study was to evaluate whether it is worthwhile to develop the target system, if the problem can be solved, and needs analysis aims to answer "What system do" question, to ensure the future developed software products to truly meet the needs of users.
Building a software system is the most difficult task is to determine what to build. Any other work will not like this as part of the work, would be so seriously affect the system then realized after the error, and after the repair would be so difficult.
Needs analysis is a very important process, it completes a direct impact on the quality of subsequent software development. In general, users are not familiar with computer knowledge, and software developers to the relevant business areas do not quite understand, between the user and the developer the same question a different understanding of the differences and idioms tend to band needs analysis to great difficulties. Therefore, adequate and effective communication between developers and users is crucial in the process of needs analysis.
Effective needs analysis usually have some difficulty, partly because the exchange obstacles, partly because users often incomplete statements on demand, inaccurate and incomplete, and possibly also constantly changing. Developers only need to abstract the existing demand in the user's help, but also need to tap the hidden demand. In addition, the abstract is also essential to the needs of future development work for the high-level logic model of the target system. Reasonable level logic model is a prerequisite for system design.
Conducting needs analysis process, the first clear demand analysis should be an iterative process. Due to the volatility of the market environment and the needs of the users themselves to ambiguity described, demand is often difficult to achieve in one step. Needs analysis is not just a job belongs to the software development life cycle early, but should also throughout the entire life cycle, it should be with the deepening of the project is constantly changing.
Further, in order to facilitate the subsequent evaluation and testing, etc., should as far as possible the needs described: In particular, in detail, may be measured and may be implemented, and based on time.
1.2 Project Risk
System Security Risk Analysis:
user's security is very important, we must protect critical information users, in order to prevent the disclosure of user information, the system as a whole will have some of the information associated with the user using asymmetric encryption algorithm RSA encryption. And regularly update the public and private keys. To ensure the security of user information
1.3 Intended Audience and reading suggestions
team members
of the audit team members of
similar systems designers
1.4 product range
based on javaEE development technology is now forming, mining ssm (spring + springmvc + mybatis) technology, the overall project uses a distributed micro service architecture, the registry selected zookeeper, using docker deploy linux server. Micro Services Framework Ali choose open-source framework dubbo. And use nginx load balancing configuration. Excluding jsp program (relieve pressure on the server), with the current mainstream html + technology to complete page of the interactive features of ajax.
1.5 References
Overall 2. System Overview
2.1 goals
designed primarily to ensure safe development of this platform is to facilitate the development of the vast campus of technical aspects related to communication and interaction, campus developers can sign-up page platform to become a platform of this Developer. Developers can submit their own written procedures and API platform interface for browsing through this platform, registered users, this platform also provides a star ranking system, the user interface will open your program or give Star. The system will recommend procedures and API interface to the user based stars. Users can also leave a message on the application, the platform will be a timely reminder application developers to view the message, to communicate with the user.
According to the plan of the project, the main goal of the project has several aspects:
-
Achieve the developer's admin interface
-
Achieve the developers to upload applications related functions
-
Achieve an open platform to build front-end system architecture
-
Achieve interstellar score, and intelligent recommendation function
-
Implement user interactive features
2.2 user classes and characteristics of
the main users: Campus developers
that they can easily be familiar with the system and use it as the main platform for the exchange of their programming
with the expected frequency of the system are: 7 * 24 hours.
2.3 Operating Environment
2.3.1 Hardware environment
multiple Linux servers.
2.3.2 software environment
1, a database using MySQL as the data storage;
2, the SSM technology as a solution system, the system has better scalability;
3, using as the system Tomcat application server;
4, the client uses the browser version, to meet the requirements of ease of use zero clients;
5, using Nginx as a load balancing server
6, using Redis as a cache server
7, using FastDfs as a distributed file system
8, as a search engine service using solr
9, using linux network IO technology epoll technology communications server
10, using log4j log management as the
2.4 limit on the design and implementation of
the design, the current system is only part of future products, we must ensure a good scalability. Realize the need for a host server, and there is no development experience and other similar products.
2.5 Assumptions and constraints (dependent)
2.5.1 product SEO rankings
In order to recover the investment of the system in the shortest possible time, need to open the market as soon as possible, to improve the SEO ranking system to help open the market as soon as possible, so as profitable as soon as possible. Lay the foundation for the next phase of development.
The need professional help.2.5.2 stable cooperation between the various modules
System is mainly composed of several modules will be divided into several types of users, stable coordination between the various modules need to be guaranteed to ensure the stable operation of the system 24 * 7, keep only periodic maintenance.
2.5.3 security system
security system is an important requirement in the current network environment, safety systems not only with its own profit, but also in relationships with a variety of user information.
Security systems, need professional help.
3. External Interface Requirements
3.1 User Interface
pursue as much as possible simple interface for intuitive delivered to the customer as much information.
Using html., Css, js + layui be written user interface
3.2 hardware interface
is unknown, the need for specific analysis of specific situations.
3.3 software interfaces
is unknown, the need for specific analysis of specific situations.
3.4 communication interface
compliant with various network protocols, to meet the needs of a variety of browsers.
Unknown, according to the specific needs of the specific analysis of the situation.
4. System features
4.1 Description
of the system according to the end user has different functions users into the following four categories:
1, Developer: upload applications, management, and update applications;
2, the average user: Browse open platform, developers use to provide application and interact with the developers;
3, user management: review applications, to provide protection for the developer, the developer proposed to solve the problem;
4, the system administrator: to maintain the normal system.
4.2 Functional Requirements
4.2.1 developer features
Description: A developer interface, modify personal information, upload the application, update the application, view the history of the application, view the user comments
4.2.2 Manager Features
Description: See the developer user, review the application, push information (for developers), announcement (open to all), the shelf applications
4.2.3 ordinary users
Description: View registration information, browsing application add Star, message, download an application or call the open interfaces, search browsing application
4.2.4 Root user function
Description: add or update administrator account, and the rest with administrator functions
4.2.5 SSO single sign-on system
Description: The JWT (java web token) way to RS256 encryption algorithm written in a single sign-on system
4.2.7 distributed file system
Description: fastDfs write file-based storage system, users store files uploaded information
4.2.8 search engine service
Description: based on written solr search engine service for users to search applications
4.2.9 instant messaging service
Description: based Epoll write instant messaging service platform for messaging
The other non-functional requirements
5.1 Performance requirements
5.1.1 accuracy of the data
as it relates to satellite data assessment, for the data class information to ensure accurate enough, the degree of accuracy.
5.1.2 Time characteristics
page refresh time can not be more than 3 seconds, jump pages directly not more than 4 seconds.
Meet user needs to quickly get the information required to optimize the page to do, so that each user can feel able to smooth quickly find the information they need.
5.1.3 Troubleshooting
page for a long time no response, warned that requires the user to refresh.
Page load time is too long, there must be prompt, to prevent users think the system problematic.
5.2 security requirements
1, the application must log on to streamline the existing basis, for exclusion for repeated logging, logging useless;
2, daily application logs must save each file to save a complete log of applications a day;
3, after application history logs must be compressed to save daily to reduce the historical log files take up hard disk space;
4, the application logs history must be preserved month (30 days), to ensure that the problem occurs, the log can be better preserved.
5.3 security requirements of
the system have sufficient defense capabilities, Defense ordinary hackers to minimize the vulnerabilities that may arise, to prevent user information from being stolen undesirable elements.
Ensure user rights are set correctly, to prevent the emergence of various ultra vires, to ensure the normal operation of the system well.
Save the user's information using asymmetric encryption algorithm RSA encryption to ensure security.
5.4 operating demand
systems can be existing staff to quickly grasp and use
The use of third-party control: the principle is not used, but must notify the proposed discussion before use by the time must be used.
5.5 software quality attributes
ease of use, ease of learning is better than or superior portability effectiveness.
5.6 business rules
product-oriented user main campus users, the client is the user terminal above the browser, not the product of a variety of special practices.
5.7 user documentation
should be concise detail, allows users to get started quickly.
