Bilqi Forum  

Geri git   Bilqi Forum > > >




Sitemize Üye Olmadan Konulara Cevap Yazabilir Ayrıca Soru Cevap Bölümüne Konu Açabilirsiniz !

Yeni Konu aç Cevapla
Seçenekler Stil
Alt 04-11-2008, 20:13   #1
Yaso - ait Kullanıcı Resmi (Avatar)
Üyelik tarihi: Jan 2008
Mesajlar: 32.967
Tecrübe Puanı: 1000
Yaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond reputeYaso has a reputation beyond repute
Standart Software Engineering


ICS 344


Subject: Commercial System


I. Introduction

The software will simulate a commercial system. The four main functions will be: Accounts,Inventories,Invoicing,Manufacturing. We are going to use the following software: Oracle Designer, Oracle Forms and Reports and Oracle Database. And for some funtions we will use C++ programming language.

II. Informatin Description

The software will represent the manufacturing, inventory, invoicing and accounting processes of a commercial system.The details,relationships are reported in the functional description part.

III. Functional Description

1. Processing Narratives
Display account statement: This function will be called from the main menu. This function contains edit, print, browse, view report and exit functions.
a) Account selection: User can select account by typing the account number and user can specify the beginning date and ending date of the transaction to view. In addition user can see the list of all accounts. If the account is not valid an error will be given to user.
b) Date specification: If beginning date and ending date does not specified all the transaction will be displayed. The format of date and time will be dd/mm/yy. If the user types another format, an error will be displayed. If the user only gives the beginning date that means accounts will be displayed until the beginning date to now.
c) Record selection: The user can select the record to see.
d) Display: The view of the account will be like Table 1.The transaction will be ordered by date and time. It can be both increasing and decreasing order. The total debit and credit will be displayed ant the beginning of the account and at the end.
e) Printing: User can print the account statement or the transactions. In addition to the record the date of printing will be printed.
f) Edit: User can edit the account. User can change all of information except account no. All the account information can be reachable from this function.
g) Save changes: After the edit function the changes have to be saved to database. The save function will backup the existing database file before the save operation. It will prevent the information loss if some problem occur during the save opertion.
h) View reports: The user can see the detailed reports by selecting the transaction. And can print the reports. The total debit and credit will be both end of the report and beginning of the report.
i) Error handling: If the user type or request some information restricted by administrator or the program itself an error massage will be displayed from the database.
j) Enter Transaction: user can add new transaction to account. The date and the time of the transaction have to be entered.

Delete an account: This function will allow user to delete all information of an account.
a) Account selection: Account selection will be typing the account number. Or the user can select the account from the account list.
b) View: User can see the account information like name, number and address. Then can delete the account.
c) Warning Handling: Before the account will be deleted a warning massage will be displayed like “All the information will be deleted! Do you want to continue?“

Create a new account: This function will allow to user to create new account. The program itself will generate the account number. All the other information will be entered by hand.

2. Restrictions And Limitations
The program will have an administrator. The administrator can restrict same users to access soma account. The other restrictions like Date & Time format are specified above. It is no possible see the records before 1990.

3. Performance Requirements
The minimum system requirements for this program: Intel Pentium Celeron 300, 64 MB RAM, enough HDD space for the database. The program will be designed to work under windows 95/98/NT/2000.

4. Design Constraints
During the coding part some design constrains can be added. But the constraints specified above are enough for now.

5. Diagrams

Screen Display

Account No: 970702043 Account Name: Mincel Corp.
Address: Hakki Erdogan Sok.
Beginning Date Ending Date
15/08/1997 30/12/1999
Date Time Explanation Debit Credit
25/11/1999 15:30
13:10 Sound Card selling
Video Card selling
Commercial software buying
Main board selling
Monitor selling
Archive program buying


$1250 $2000

Total $8750 $14850




Functional Description
a. Functional Partitioning
. New good identification
. Inventory Listing
. Identification code list
. Viewing/editing of an inventory card
. Removing an inventory card
. Good Input
. Good Output
b. Functional Description
1. New Good Identification:
a. Processing Narrative
Here a new good (may be product, semi-product or raw material) is defined to the system. At the end, a new code which has one letter (R, P, or S) as first character which identifies whether it is a raw material, product or semi-product and a three digit number which is the last element's number part defined to the system as R, P or S plus one.

There are 3 main elements:
1. Raw material
2. Products
3. Semi-Products

Raw materials are the elements that are used to manufacture the products. They are bought from other companies (invoiced to that company). Products are manufactured by manufacturing department and their related cost is defined by that department. Also the semi-products are the same as products.
Every goods holding place in inventory has to have a unique code (can be thought as a primary key). This code will identify that good's attributes clearly.
In inventory, the only thing is to keep records of all input and outputs of goods. These can be raw materials (which are used by manufacturing department to produce products), products (which are sold to companies which have previously recorded and have an account) or semi-products.
When defining a new good, first its type (raw material, product or semi-product) is defined. ID is given automatically by the system. Unit cost is not necessarily defined at the beginning. It is defined by the manufacturing department (a product) or invoicing department (maybe a raw material). Then a good name is defined into the system. In description part, the properties related to the good are defined.
At the end, by pushing the button ‘Save’, the operation of the defining a new good to the system is completed.
b. Restrictions and Limitations
If the good name was previously defined to the system, then an error message showing the duplication of the good name is shown at the screen. Or if the good type is not recognized (i.e. not R/P/S) then it will be reported as an error message. Invoicing department cannot invoice any undefined good.

c. Performance Constraints
After defining the good into the system, an empty identification page will be appeared in 1-2 seconds. When more of goods are defined to the system this time can be altered. These assumptions are on the systems with Pentium II/III CPU, 32MB or more RAM, Windows 95/98/Me or Windows NT/2000.
d. Supporting Diagrams
I. Screen Display

II. Data Flow Diagram

III. Control Flow

2. Inventory Listing
a. Processing Narrative
Here all the goods in inventory are shown by the order of their IDs. There are four main columns. These columns are ID, name, cost and amount. Amount is the number of goods in inventory.
At the beginning, two choices will be presented to the user. One of which is normal will give all the normal goods in the inventory. The other one will give the list of returns. These returns could be defect-based.
b. Restrictions/Limitations
The return list and the normal list are two different lists. They cannot be shown in the same list. These list can only hold the goods(whether return or normal goods) that take place in the inventory.
c. Performance Constraints
Same requirements as the previous one. According to the information amount, the creation of the list after choosing one(return list or normal list) will take 1 or more seconds.
d. Supporting Diagrams
I. Screen Display

II. Data Flow Diagram

III. Control Flow

3. Identification Code List
a. Processing Narrative
In this part, all the goods are shown with their ID numbers. This list is ordered by the name of the good. The goods can be raw materials, products, or semi-products. These goods do not have to exist in the inventory.
b. Restrictions/Limitations
No restrictions or limitations are available.
c. Performance Constraints
Same performance constraints as inventory listing are also available for this part.
d. Supporting Diagrams
I. Screen Display

4.Viewing/Editing Inventory Card

a.Processing Narrative

The inventory card of an inventory will be related to its properties.There will be a list of inventory cards including ID and NAME of the inventory.This is important especially for products and semi-products.So each product or semi-product will be related to a descriptive file which depicts it.


The user will only see the inventory card of recognized (previously defined) good by the system.

c.Performance Constraints

The systems will require Pentium II/III CPU, 32MB or more RAM, Windows 95/98 or Windows NT/2000.

d.Supporting Diagrams

I. Screen Display

II. Data Flow

III. Control Flow

5.Removing an Inventory Card
a.Processing Narrative
The inventory card were available for the existing inventory.So What will be done in this part is to delete the inventory card from list and related descriptive file when an inventory is wanted to be removed from the system.
b.Restrictions /Limitations
The user can only remove the inventory card of inventory whose amount is zero
c.Performance Constraints
The systems will require Pentium II/III CPU, 32MB or more RAM, Windows 95/98 or Windows NT/2000.
d. Supporting Diagrams
I. Screen Display

II. Data Flow

II. Control Flow

7.Good Input

a.Processing Narrative

If an input(inventory) is entered to the store the inventory list table will be updated.The related input will be increased by the amount entered to the store.(Also unit cost will be updated if it changes)

b.Restrictions /Limitations

The input cannot be entered if t doesn’t exist in the list(not recognized).In this case it will be first identified to the system.
c.Performance Constraints

The systems will require Pentium II/III CPU, 32MB or more RAM, Windows 95/98 or Windows NT/2000.

d. Supporting Diagrams
I. Screen Display
After selecting input from main menu ,following comes….

II. Data Flow

II. Control Flow

8.Good Output

a.Processing Narrative
If an output(inventory) exits from the store, the inventory list table will be updated.The related input will be decreased by the amount exited from the store.

b.Restrictions /Limitations
User cannot desire more than existing amount.
c.Performance Constraints

The systems with Pentium II/III CPU, 32MB or more RAM, Windows 95/98 or Windows NT/2000.

d. Supporting Diagrams
I. Screen Display

II. Data Flow

III. Control Flow


Functional Description
a. Functional partitioning:
1. Organizing and Printing an Invoice
2. Displaying a Voucher

b. Functional Description
a) Processing Narrative:
From the Main Menu users will be able to organize an invoice. There will be a “Create invoice” button on the main menu. Since there are two types of invoices user will enter the type of the invoice whether it’s a kind of expense invoice (there will be expenses such as electricity and there will be expenses to buy raw materials.) or an invoice that’s from this company to someone else. (Sales, servicing, etc.)
Each invoice will have an “Invoice No” in order to be able to make each distinct. Date will be written for making queries on date. (Such as user will be able to see the invoices written on 10.6.2001). The user will enter to which company the invoice is for. There will be line no's on the Invoice. A general explanation column about the product or service will be on the invoice. A product no column will appear for taking the Unit Price of the good or service from the database on Unit Price table. There will be Quantity column in order to calculate the total amount for goods sold or services. Total column will show the total amount debited by the vendor on that product. Line no’s, Unit Prices and Total will be automatically written on the invoice form. The user will enter others. At the end (when the user finishes entering data on the invoice) the total amount for all (written on the invoice form) will be calculated.
The goods that are sold will be told to the inventory department. The amount of goods sold will be reduced from the inventory tables. The transaction (that appeared on the invoice) will be entered to the Transaction file. Accounts department keeps transaction file.
At the end user will be able to save that invoice so the data that’s going to be passed to the database will be saved. Invoices will be written to the transaction file in order to enter the debits and credits into accounts. Each item in the invoice will be saved into accounts.
After the invoice is saved the user will be able to print that invoice. There will be a “Print invoice” button on the main menu. If the invoice was written before and the window for it is closed, sytem will ask the user invoice no. The system will bring an invoice form that I mentioned in the “create invoice” function from the database. If the user enters an invalid invoice no there will appear an error message.And the system will not permit user to print an invoice form.

b) Restrictions/limitations :
The user has to enter the data that` s required to organize the invoice. Any empty field will be reported by an error message. Invoices that are older than 1 year will not be accessible. If the user wants to print an invoice that’s not available(maybe with a wrong invoice number) an error message will appear. If the invoice contains a product that’s not available in the inventory that invoice will not be saved and the user will be informed that the invoice is not proper.

c) Performance Constraints:
The new line no will be filled by the program within 2 seconds after the user finishes writing on the line. The unit product will be filled after the user enters the Product no. These constraints are assumed on a Pentium II or III system with 32MB RAM under Windows 98 or Windows NT or Windows 2000 Professional OS.

d) Design Constraints:
All are described above.
e) Supporting Diagrams:

I. Screen Display

Invoice no:97070 Date: 10.06.2001 Explanation: Invoice from Mincel Corp. to A comp.(Sales Invoice)

Line No: Explanation No Quantity Unit
Price Total
2 Printer
Modem 1556
1221 1
2 $90
$70 $90
TOTAL $230

II. Data Flow Diagram

III. Control Flow

Display OK no
Create invoice stat.

2.Displaying a Voucher
a)Processing Narrative
From the main menu users will be able to display a voucher .Vouchers will be displayed according to date. User will see the transactions on that date. Voucher no will be given by the program. User will enter the date to see the transactions on that date. After user entered the date the items will be displayed according to the columns line no, account no, explanation ,debit,credit.The data that’s searched will be brought from the database from the accounts table and transaction file.

b) Restrictions/limitations : The user has to enter the date to display the voucher. Record older than 1 year will not be accessible.

c)Performance Requirements:
The data will be displayed by the program within 2 seconds after the user finishes writing the date. This constraint is assumed on a Pentium II or III system with 32MB RAM under Windows 98 or Windows NT or Windows 2000 Professional OS.

d) Design Constraints:
Expressed in the preceding.
e) Supporting Diagrams:

I. Screen Display

Voucher no:9875 Date: 10.06.2001 Explanation: Transactions from Mincel Corp.

Line No: Explanation Account No debit credit balance
2 purchased
Sold 1556
$70 $90

II. Data Flow Diagram:

III.Control Flow

Display voucher stat.


Introduction :

The goals of manufacturing function is to calculate the cost of the product that is planned to produce, the details of that products , and to get the list of the products that are being produced.

Functional Partitioning :

• Functional Partitioning

• Manifactuirng cost
• Manifacturing listing
• Products
• Semi-products
• Manifacturing status
• List of all produced elements and their details

Functional Description :

Processing Narrative :

Manifactoring cost : the details of a new product, that is planned to produce, are described. It is described how many materials or semi materials are needed, how much it costs per each unit of product.. All products that are being produced must have unique product id. Nevertheless all materials that are used during the manifacturing must have unique id, too.

There are two main elements :
• Semi-products
• Raw-material

Manifacturing Status : a database is hold to include the datas of products which are in manifacturing process. If the manifacturing process is finished for a product, the details for this products must be deleted from the Manifacturing Status database.

List of produced elements & thier details : the list of products that are passed from the manifacturing process are hold in the database.This means, all products in this database are produced and sent to the inventory.

Restrictions & Limitations :

Manifactoring Cost : for each unit of product , a new database table must be created. This table must be include the following attributes.

• Inventory_product_id
• Number_unit
• Unit_cost
• Unit_total_cost
• Date

No more details can be entered into these tables.

Manifacturing Status : for each unit of product the followinf details are needed.

• Product_id
• Start_date
• Finish_date
• Unit_produced
• Unit_must_be_produced

This table only shows the products that are in manifacturing process. This data does not include the details of all products.

List of produced goods & their elements : all goods that are produced must be entered this database. All information about produced goods and sent goods to the inventory are stored in this database. The following details must be defined.

• Product_id
• Finish_date
• Total_cost
• Unit_produced
• Description
Yaso isimli Üye şimdilik offline konumundadır   Alıntı ile Cevapla


Konuyu Toplam 1 Üye okuyor. (0 Kayıtlı üye ve 1 Misafir)

Sizin Yeni Konu Acma Yetkiniz var yok
Sizin Konu Yanıtlama Yetkiniz var
You may not post attachments
You may not edit your posts

BB code is Açık
Smileler Açık
[IMG] Kodları Açık

Gitmek istediğiniz klasörü seçiniz

Benzer Konular
Konu Konuyu Başlatan Forum Cevaplar Son Mesaj
Microsoft Software Inventory Analyzer 4.0 Yaso Araçlar 0 06-25-2008 13:48
Free Medical Dictionary Software 1.0 Yaso Araçlar 0 06-24-2008 23:40
Jiangmin Antivirus Software KV2006 Yaso Araçlar 0 06-24-2008 09:44
SecureIT Encryption Software 3.1.3 Yaso Araçlar 0 06-18-2008 18:10
Auto Backup Software Yaso Araçlar 0 06-17-2008 19:19

Şu Anki Saat: 19:28

İçerik sağlayıcı paylaşım sitelerinden biri olan Forum Adresimizde T.C.K Madde ve 5651 Sayılı Kanun'un 4.cü maddesinin (2).ci fıkrasına göre TÜM ÜYELERİMİZ yaptıkları paylaşımlardan sorumludur. hakkında yapılacak tüm hukuksal Şikayetler ve dan iletişime geçilmesi halinde ilgili kanunlar ve yönetmelikler çerçevesinde en geç 1 (Bir) Hafta içerisinde yönetimi olarak tarafımızdan gereken işlemler yapılacak ve size dönüş yapacaktır.
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Lite) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.

Android Rom

Android Oyunlar

Android samsung htc

Samsung Htc

Nokia Windows