Escolar Documentos
Profissional Documentos
Cultura Documentos
Pim 6
Pim 6
2016
UNIP INTERATIVA
1505231 - 1500492
1 Semestre
2016
RESUMO
Por fim, os prottipos de tela foram desenvolvidos com base nos atributos das
classes do diagrama e aos requisitos no funcionais.
This document shows a project that has Systems Analysis aspects Object Oriented,
in order to initiate the development of a system for the company Model Autoparts,
which hired the services of the company Pacific Solutions to remedy its shortcomings
in its processes: control inventory and incorrect calculations in the commission of
vendors.
The demonstration takes place through the survey and specifications of use cases,
use case diagrams, requirements, class diagrams, business rules and interface
prototypes (layout screens).
Use cases are representations of externally observable features, the system is based
on sales and inventory control of its products, so were identified as use cases:
Product registration and vendor registration (each has the option to change, delete
and consultation), joined to launch an application and may select one or more
products and assign a salesman, salesmen commission calculation on top of the
application (this is done automatically at the time of checkout).
It was also developed a case of user registration use, where there are three types:
restricted user, default user and system administrator. Restricted users have access
only to query features, as well as the default user and system administrator.
Standard User is responsible for launching an application and system administrator
for registering products, sellers and new users.
The use case diagram shows system activities for the types of users in a stream, and
specifications are detailed internal processes (validations, prints, chosen options).
The types of requirements for this system are non-functional requirements (usability),
which was specified standard of entries, access to data, installation and user manual,
authentication, security (encryption), hardware and tools for the development, where
turning to the quality of service.
For the class diagram classes were specified: product, vendor, order, order item, the
user (and user parent class restricted default user and system administrator,
generating an inheritance). Each class has been assigned to a representation of
multiplicity.
Finally, screen prototypes to have been developed based on the attributes of the
class diagram and nonfunctional requirements.
The methodologies used in the preparation were the Systems Analysis classes
Object Oriented, Human Machine Interface and professional knowledge, and a job
that optimizes development time and ensures quality.
SUMRIO
1 INTRODUO ................................................................................................. 6
4.7 Ambiente.........................................................................................................21
4.9 Hardwares.......................................................................................................23
5 DIAGRAMA DE CLASSES.............................................................................24
7 CONCLUSO.................................................................................................31
8 REFERNCIAS.............................................................................................32
6
1 INTRODUO
Uma loja chamada Modelo Autopeas, localizada no Rio de Janeiro, possui processos
falhos e deficientes em seu trabalho, com muita ao humana no registro de
informaes, descontrole do estoque, gerao de clculos incorretos no valor de
comisso de vendedores e atrasos nas compras de produtos para reposio de
estoque. Seu proprietrio, visando corrigir esses processos, contratou a empresa
Pacific Solutions para criar um software que possa sanar essas deficincias em seus
processos.
O objetivo para realizao desse trabalho identificar os casos de usos, assim como
elaborar os modelos de casos de uso, os relacionamentos entre as entidades
(classes) necessrias para o desenvolvimento do sistema, descrever os requisitos no
funcionais e de usabilidade, identificar e descrever o contexto de uso e regras de
negcio, elaborar os diagramas de classes de anlise e os prottipos das telas
principais.
Com isso ser possvel desenvolver um sistema slido, com o mnimo de erros e
que se adeque e resolva problemas nos processos da loja, alm de garantir a
usabilidade do usurio, regras de negcios bem elaborados, prazos bem definidos e
a satisfao do cliente.
.
7
Fluxo Principal:
Fluxo principal:
Fluxo principal:
Fluxo principal:
Fluxo principal:
Fluxo principal:
Fluxo principal:
4 REQUISITOS NO FUNCIONAIS
- Se algum dos campos do registro for uma data, a pesquisa avanada ainda
permitir a filtragem de registros atravs do fornecimento de um intervalo de
datas, filtrando registros cujo campo de data esteja no dado intervalo.
16
Todo acesso a dados dever ser realizado via ODBC de forma a reduzir o
acoplamento entre cdigo e banco de dados.
17
4.7 Ambiente
- Aplicao Cliente: Dever ter como alvo principal o Windows 10, com a
linguagem php instalado e o servidor Web Apache.
4.9 Hardwares
5 DIAGRAMA DE CLASSES
25
7 CONCLUSO
Neste projeto conseguimos analisar todas essas fazes para sanar uma dificuldade
em um dos processes do nosso cliente, a loja Modelo Autopeas, localizada no
Rio de Janeiro.
8 REFERNCIAS
BECK., and Kent. TDD Desenvolvimento Guiado por Testes. Bookman, 2010.
VitalBook file. Disponvel em: Acesso em: 02 de abril de 2015.