The document provides information about the design round of the Yarl Geek Challenge IT talent competition. It explains that software design is important to illustrate the development plan, map out requirements, and help competitors and judges understand the overall system picture. In the competition, design submissions should include an overall system design, lower-level diagrams, technology stack details, and innovative design techniques. Judges will evaluate submissions based on cohesion, comprehensiveness, relevance, innovation, and technology suitability. Competitors should prepare to explain and defend their designs during questioning.

2. Yarl Geek Challenge
The IT talent search

3. DESIGN ROUND

4. What is Software Design
 Sketch of the Software development plan in
some form
 Software design helps to bridge the
requirements with the development
 In industry, software design is essential for
bigger projects
 Is it important for the smaller projects?

5. Why it is important
 It helps to illustrate the plan in an easier way
 Maps are easier to understand than the words
explaining a route
 Software design is the developer's medium to
understand the requirements
 It helps to get the overall picture

6. Why it is in the Geek Challenge
 Competitors can express their plan through the
design
 Judges and the competitors can have different
views about the scope of the selected project
 Design round will give the competitors a chance
to explain their plan
 It will help the audience to get a better picture
 Competitors will get a chance to learn during the
competition period

7. What is expected to express
 Overall design of the system (the big picture)
 Lower level diagrams to explain the heart of
the system
 Important logic of the system can be explained
through sequence diagrams or activity diagrams
 Technology stack
 What is the technologies to be used
 Justification for choosing them

8. What is expected to express
 Any more designs which can help to explain
the system's design in a better way
(Unconventional approach)
 Any fancy business process diagrams :)

9. What judges would expect
 Cohesion
 How comprehensive was it
 How well it has covered the project scope
 How well Over all design is expressed
 How easy it was to understand
 Relevancy between the project requirements and
design
 Whether each of the design aspects are relevant to
the proposed requirement in the technical market

10. What judges would expect
 Innovative
 Usage of the innovative design techniques or
tools to illustrate the design
 Chosen technologies
 How suitable was the technology stack
 Whether competitors are aware of the latest
trend in the technical market

11. What judges might ask from you
 Can ask you to elaborate more about your
design
 Judges might try to find the flaws in your
design and ask you to defend your design
decisions
 Judges would provide a different scenario and
ask you to draw a design on the white board
 So be ready tackle the judges :)

12. Some suggestions to score
 Get together as team and discuss
 Make use of your mentor
 You need to show difference from others to
score more
 It is a competition
 So think out of the box
 Plan it well
 Interview previous year's participants

13. Thank you!