Member Avatar for sukhmani

hello

I'm making chess in c++. I have to submit a report and it should include system development life cycle and detailed design....if some one cud please help me out wid it....
plz mail me at[EMAIL=<snip>
sukhmani

  • 3 Contributors
  • 2 Replies
  • 107 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by stymiee

Dani AI

Generated

To make the requested SDLC and detailed design usable for a student project, break the work into clear phases and concrete deliverables that match what will be written in the report.

Start with a short SRS (requirements): list functional requirements (legal move generation, move validation, game-state checks, save/load, undo, optional AI, optional GUI/network), non-functional requirements (performance, portability, C++ standard target). For Analysis, include use cases (make move, undo, promote, time control) and acceptance criteria for each. For Design, produce a UML class diagram, sequence diagrams for move application and undo, and a data-dictionary describing board representation.

A compact detailed-design decomposition:

  • Core model: Board, Piece, Move, MoveHistory, GameState.
  • Rules/engine: MoveGenerator/Validator, CheckDetector, GameEvaluator.
  • UI: CLI or GUI adapter that observes GameState.
  • Optional: Engine/AI separated by a Strategy interface, Persistence for save/load, Network module for two-player over sockets.
    Prefer starting with an 8x8 array representation (simpler to test), then refactor to bitboards only if performance becomes essential. Use RAII and smart pointers (C++11+) for resource safety. Consider Command for undo, Strategy for AI, and Observer for UI updates.

Example minimal class skeleton:

struct Move { int fromR, fromC, toR, toC; char promotion; };
class Board {
  uint8_t squares[8][8];
  bool applyMove(const Move&);
  void undoMove();
};

Testing and common pitfalls: include unit tests for pawn moves, castling, en-passant, promotion, check/checkmate, stalemate, threefold repetition and 50-move rule. Typical bugs are incorrect state updates for castling/en-passant, failing to detect discovered checks, and not restoring state correctly on undo. Capture reproducible failing positions and write regression tests.

Deliverables for the report: SRS, design diagrams, key class interfaces, test plan with cases and results, timeline/milestones, and a short user guide. : clarify scope early (engine vs UI vs network). : keep the implementation your own; use this plan as a blueprint and bring focused code questions back for help.

Recommended Answers

All 2 Replies

Member Avatar for fulyaoner

hello

I'm making chess in c++. I have to submit a report and it should include system development life cycle and detailed design....if some one cud please help me out wid it....
plz mail me at

sukhmani

Do you have any idea about level of difficulty?
Will it be a simulator, or 2 players game...

It is not easy to write a chess from scratch as I know.

Member Avatar for stymiee

Sorry but we don't do work for members here. We only help them. So you either need to write some code and ask specific questions when you need help or try to hire someone.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.