0% found this document useful (0 votes)
149 views16 pages

SRS Image Viewer & Analyzer

The document describes the Waterfall model approach for system development. It lists the typical phases of system development in the Waterfall model: analysis, design, implementation, system testing, and maintenance. It then provides details about analyzing the requirements for developing an image viewer and analyzer application based on the Waterfall model.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
149 views16 pages

SRS Image Viewer & Analyzer

The document describes the Waterfall model approach for system development. It lists the typical phases of system development in the Waterfall model: analysis, design, implementation, system testing, and maintenance. It then provides details about analyzing the requirements for developing an image viewer and analyzer application based on the Waterfall model.
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 16

System development model:

WATERFALL MODEL approach for the system development.

This model displays the various phases that a system has to phase during its development.
These phases are:

1. Analysis phase: this phase consists of two sub phases: project planning and requirement
definition. The outcome of this phase is the system definition.

2. Design phase: this phase is concerned with identifying the software component,
specifying the relationships among components, specifying software structure and design
structure.

3. Implementation phase: this phase involves translation of design specification into source
code.

4. System testing phase: errors discovered during the implementation phase include logical
errors in the algorithms, error in data structure layout, and others. System testing involves
two kinds of testing: integration and acceptation testing

5. Maintenance phase: this phase involves enhancement of the capabilities, adaptability of


the software with the new processing environments, and correction of the software bugs.
ANALYSIS PHASE

To develop a Image Viewer & Analyzer Application:

About the proposed system (Assigned project):-

The objective of this project is to develop an image viewer & analyzer application to
provide the facility to the end user for viewing the different images (BMP, JPG, JPEG, PNG,
GIF, TIFF, PCX) & analyze the images such as the file type, file header, size, compression,
pallet entry, storage format etc.

Goal for the system and project:-

Goal of the project is to provide a system with full accuracy.

Objective of the project:

The main objective of the project is to provide facility to the client that client can view &
analyze an image file for the different kind of purposes.

Constraints on the system and the project:-

1. Time constraint: - The available time to develop the proposed system is one month and
fifteen days.
2. Software constraints:- The proposed system is to be developed from the available
software and application tools.
Development environment:-

Hardware environment:
PC, Desktop Speakers

Software environment:
Front-end designing software will be VC++ 6.0.

Other tools that are used in the development of this project are:
MS Word is used for documentation purpose.
Notepad to design html help files as user manual.

Operating environment:
The operating system on which this system will be developed is Windows NT/2000
Server/XP. These are the Network operating system that supports multi user
environment.
SYSTEM DESIGN:-

The top down approach is been preferred to design this system since this is a small
project and not enough detail is been provided during requirement specification.

CONTEXT DIAGRAM:

Context diagram of the system is shown in figure. It gives an overview of basic input,
processes and output. It consists of only one process, data flows, and entities. It determines the
boundaries of the system.

E
D

Image Data
Image Data
DISPLAY IMAGE
L
I IMAGE FILE IMAGE
S VIEWER & DISPLAY IMAGE
ANALYZER
SET CONSRAINTS Analyzed
Image Data
Login Data

CONTEXT DIAGRAM
MODULE DESIGN:

A module is a logical construct for grouping classes, associations and generalizations. It


captures perspective or view of a situation. When a system is decomposed into modules, it able
to describe the overall modular structure precisely and the relationship among the individual
modules. The methods, which have been followed to show the relations among modules, are:

The USES relation : One module may use another module.


The IS_COMPONENT_OF relation : One module may be a component of another
Module; conversely a module may comprise
Of several modules.
STRUCTURE CHART:

The structure chart is shown below :

BMP JPG JPEG GIF PNG TIFF PCX

IMAGE
VIEWER

VIEW IMAGE IMAGE ANALYZER

Image Data
Image Data Display
Analyzed
Data

IMAGE IMAGE DISPLAY


FILE FILE IMAGE FILE

Structure Chart
DATA FLOW DIAGRAM:

DISPLAY IMAGE
APPLICATION

DISPLAY
IMAGE

No Yes

IMAGE VIEWER
LOGIN
PROCESS
IMAGE ANALYZER
Image File

ANALYZ
E IMAGE

INPUT
IMAGE
FILE OUTPUT DATA

DATA FLOW DIAGRAM:


IMPLEMENTATION PHASE:-
USER INTERFACE DESIGN:

bool UserLogin();
void FileOpen(CString fileName);
void FileClose();

IMAGE VIEWER MODULE :

void DisplayImage(CString fileName);


void ViewBMPFile();
void ViewJPGFile();
void ViewJPEGFile();
void ViewGIFFile();
void ViewPNGFile();
void ViewPCXFile();
void ViewTIFFFile();

IMAGE ANALYZER MODULE :

void AnalyzeImage(CString fileName);


void AnalyzeBMPFile();
void AnalyzeJPGFile();
void AnalyzeJPEGFile();
void AnalyzeGIFFile();
void AnalyzePNGFile();
void AnalyzePCXFile();
void AnalyzeTIFFFile();
void DisplayAnalyzeData();
TESTING:-

The testing process is divided in to various levels. It starts with Unit testing that
comprises the set of testing that are performed by the individual programmers before performing
integration testing. The programmer tests each small module individually. We perform four
categories of tests:

• Functional tests
• Performance test
• Stress tests
• Structure test

The next level of testing is system testing that involves two kinds of activities:

• Integration testing: this involves integrating the small modules and then
performing testing on them.
• Acceptance testing: during this all the small modules are integrated and the final
testing is done on the final product. This also performs the four categories of
testing on the final product to validate its reliability.
MAINTENANCE:

This activity involves making enhancement in the presently designed system by adding
something new to it or updating some parts of the present system, adapting to new environment.
In future if requirement arises one can introduce the video functionalities like transferring video
frame, playing video frames etc.
Image File Header Formats
BMP, PCX, JPEG, FLI/FLC, and AVI files include headers that define the image size, number of
colors, and other information needed to display the image. Fastgraph provides functions for
reading the image headers and retrieving their more useful items. However, there may be times
when you need additional information stored in the file header. This section provides full details
about the structure of the image file headers. In the tables that follow, we'll assume all offsets
start at zero, all field sizes are in bytes, and all numeric values are stored with the least
significant byte first.

• Image File Header Formats


• BMP (Windows) Header Format
• BMP (OS/2) Header Format
• PCX Header Format
• JPEG Header Format
• FLI/FLC Header Format
• AVI Header Format
BMP (Windows) Header Format
Windows BMP files begin with a 54-byte header:

offset size description

0 2 signature, must be 4D42 hex

2 4 size of BMP file in bytes (unreliable)

6 2 reserved, must be zero

8 2 reserved, must be zero

10 4 offset to start of image data in bytes

14 4 size of BITMAPINFOHEADER structure, must be 40

18 4 image width in pixels

22 4 image height in pixels

26 2 number of planes in the image, must be 1

28 2 number of bits per pixel (1, 4, 8, or 24)

30 4 compression type (0=none, 1=RLE-8, 2=RLE-4)

34 4 size of image data in bytes (including padding)

38 4 horizontal resolution in pixels per meter (unreliable)

42 4 vertical resolution in pixels per meter (unreliable)

46 4 number of colors in image, or zero

50 4 number of important colors, or zero


BMP (OS/2) Header Format
OS/2 BMP files begin with a 26-byte header:

offset size description

0 2 signature, must be 4D42 hex

2 4 size of BMP file in bytes (unreliable)

6 2 reserved, must be zero

8 2 reserved, must be zero

10 4 offset to start of image data in bytes

14 4 size of BITMAPCOREHEADER structure, must be 12

18 2 image width in pixels

20 2 image height in pixels

22 2 number of planes in the image, must be 1

24 2 number of bits per pixel (1, 4, 8, or 24)


PCX Header Format
PCX files begin with a 128-byte header:

offset size description

0 1 manufacturer byte, must be 10 decimal

1 1 PCX version number

0 = PC Paintbrush version 2.5

2 = PC Paintbrush 2.8 with palette information

3 = PC Paintbrush 2.8 without palette information

4 = PC Paintbrush for Windows

5 = PC Paintbrush 3.0 or later, PC Paintbrush Plus

2 1 run length encoding byte, must be 1

3 1 number of bits per pixel per bit plane

4 8 image limits in pixels: Xmin, Ymin, Xmax, Ymax

12 2 horizontal dots per inch when printed (unreliable)

14 2 vertical dots per inch when printed (unreliable)

16 48 16-color palette (16 RGB triples between 0-255)

64 1 reserved, must be zero

65 1 number of bit planes

66 2 video memory bytes per image row


JPEG Header Format
Strictly speaking, JPEG files do not have formal headers, but fg_jpeghead() and
fgi_jpeghead() return relevant information from the file's start of frame segment. We
call it a header for consistency with other image file formats.

offset size description

0 2 JPEG SOI marker (FFD8 hex)

2 2 image width in pixels

4 2 image height in pixels

6 1 number of components (1 = grayscale, 3 = RGB)

7 1 horizontal/vertical sampling factors for component 1

8 1 sampling factors for component 2 (if RGB)

9 1 sampling factors for component 3 (if RGB)

You might also like