Академический Документы
Профессиональный Документы
Культура Документы
4 ANALYSIS
T1: COMMUNICATION
T2: PLANNING
T3: MODELING
T21: ESTIMATION
T31: ANALYSIS
T32: DESIGN
!(
VACOE, AHMEDNAGAR
4)+ 4"1 P!#$ %t -#!, .! a,&#/* St!'%t'! 0A*a(12)23
4"2 Ta2,2
T!) Searching for project definitions. T*) 'e+uired literature collection. T,) -iterature review. T ) Finali$ation of algorithms to be implemented. T.) Project finali$ation and Synopsis Submission T/) 'e+uirements gathering and validation. T0) System design. T1) System analysis. T2) 3&- &odeling T!() 'isk analysis and management. T!!) 4mplementation of methods for feature extraction. T!*) %reation of tables in database T!,) Storing images in logical database in the form of extracted feature vector along with their path. T! ) 4mplementation of 5%' training algorithm. T!.) %reation of 634. T!/) 5%' testing T!0) Perform unit testing. T!1) %ombine modules and perform integration testing. T!2) &odifications in 4mplementation if necessary. T*() 7elivery of increment ! to user along with necessary documentation and taking feedback. T*!) 8s per feedback, perform necessary modifications for increment *.
!!
VACOE, AHMEDNAGAR
!*
VACOE, AHMEDNAGAR
4"3"1 T)7 ()* Cha!t
4)+ 4"2 T)7 L)* Cha!t1 8A%t'a( Da129 < 4ndicates &ilestone &!) Finali$ation of algorithms &*) System 7esign
!,
VACOE, AHMEDNAGAR
4)+ 4"3 T)7 L)* Cha!t2 8E:p %t &9 < 4ndicates &ilestone &!) Feature =xtraction &*) 5%' Training &,) 5%' Testing
VACOE, AHMEDNAGAR
4"3"2 P!#$ %t Ta5( Ta5( 4"2 P!#$ %t Ta5( Ta2, *# T! T* T, T T. T/ T0 T1 T2 T!( T!! T!* T!, T! T!. T!/ T!0 T!1 T!2 T*( T*! Sta!t)*+ t)7 E:p %t & A%t'a( !!>(0>!! !1>(0>!! *.>(0>!! (!>(1>!! (/>(1>!! !!>(1>!! !2>(1>!! (!>(2>!! !.>(2>!! ,(>(2>!! (2>(!>!* (2>(!>!* (,>(*>!* (/>(*>!* (2>(*>!* *2>(*>!* (.>(,>!* !*>(,>!* !2>(,>!* */>(,>!* (*>( >!* !*>(0>!! (/>(1>!! !,>(1>!! !2>(1>!! *.>(1>!! ,(>(1>!! (0>(2>!! !,>(2>!! ( >!(>!! ! >!(>!! : : : : : : : : : : : E*&)*+ T)7 E:p %t & A%t'a( !0>(0>!! * >(0>!! ,!>(0>!! (.>(1>!! !(>(1>!! !1>(1>!! ,(>(1>!! ! >(2>!! *2>(2>!! (2>!(>!! (!>(*>!* (!>(*>!* (.>(*>!* (1>(*>!* *1>(*>!* ( >(,>!* !!>(,>!* !1>(,>!* *.>(,>!* (!>( >!* !*>( >!* (0>(1>!! !*>(1>!! !1>(1>!! *,>(1>!! *2>(1>!! (/>(2>!! ! >(2>!! (*>!(>!! ! >!(>!! !2>!(>!! : : : : : : : : : : : D 6 (#p !2 A22)+* & 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7* 7*,7, 7!,7* 7*,7, 7!,7*,7, 7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, 7!,7*,7, R 7a!,
VACOE, AHMEDNAGAR
!/
VACOE, AHMEDNAGAR
. .!.* %lass 7iagram 4n design specification it can be used to specify interfaces and classes that will be implemented in an object oriented program.
!0
VACOE, AHMEDNAGAR
. .!., Se+uence 7iagram 8 se+uence diagram is a graphical view of a scenario that shows object interaction in a time:based se+uence. Se+uence diagrams establish the roles of objects and help provide essential information to determine class responsibilities and interfaces. This type of diagram is best used during early analysis phases in design because they are simple and easy to comprehend. Se+uence diagrams are normally associated with use cases.
!1
VACOE, AHMEDNAGAR
. .!. 8ctivity 7iagram 8ctivity diagrams are very similar to a flowchart because you can model a workflow from activity to activity.
!2
VACOE, AHMEDNAGAR
. .!.. State &achine 7iagram State chart diagrams model the dynamic behavior of individual classes or any other kind of object. They show the se+uences of states that an object goes through, the events that cause a transition from one state to another and the actions that result from a state change.
*(
VACOE, AHMEDNAGAR
4"4"2 4'*%t)#*a( M#& ()*+ . .*.! 7ata Flow 7iagram 7ata flow diagram 97F7) is also called as ?#ubble %hart@ is a graphical techni+ue, which is used to represent information flow, and transformers those are applied when data moves from input to output. 7F7 represents system re+uirements clearly and identify transformers those becomes programs in design. 7F7 may further partitioned into different levels to show detailed information flow e.g. level(, level! etc.
8pplication 7atabase
3ser 4nput
Feature =xtraction
=xtracted Feature
5utput File
*!
VACOE, AHMEDNAGAR
4)+ 4"1B" Data 4(#/ D)a+!a70( 6 ( 13 . .*.* %ontrol Flow 7iagram The large class of applications having following characteristics re+uires control flow modeling<: The applications those are driven by the events rather than data. The applications those produce control information rather than reports or displays. The application those process information in specific time.
4nput Text
7isplay 5utput
Feature =xtraction
4dentify %haracters
Storing Feature 4n 7#
Feature 4n 7#
Test 5%'
Train 5%'
4nput Text
Feature =xtraction
**
VACOE, AHMEDNAGAR
4)+ 4"11" C#*t!#( 4(#/ D)a+!a7
4"4"3 A!%h)t %t'! M#& ()*+ . .,.! %omponent 7iagram %omponent diagrams provide a physical view of current model. 8 component diagram shows organi$ations and dependencies among software components, including source code components, binary code components, and executable components. These diagrams also show externally:visible behavior of components by displaying interfaces of the components.
*,
VACOE, AHMEDNAGAR
. .,.* 7eployment 7iagram 8 deployment diagram shows the allocation of processes to processors in the physical design of a system. 8 deployment diagram may represent all or part of the process architecture of a system.
VACOE, AHMEDNAGAR
*.